-
Notifications
You must be signed in to change notification settings - Fork 212
rsna 2016
Nicolas Rannou edited this page Nov 25, 2016
·
15 revisions
- Description of the platform/product:
- name and version of the software? AMI (Medical Imaging Javascript Toolkit) - v0.0.12+
- free? yes
- commercial? no
- opensource? yes - Github repository
- what DICOM library do you use? dicomParser
- Description of the relevant features of the platform:
- are both single and multiple segments supported? yes
- how are the overlapping segments handled? yes if loaded in separate files. No if overlapping segments are part of the same segmentation object.
- do you support both BINARY and FRACTIONAL segmentation types? only BINARY (need test dataset for FRACTIONAL)
- do you render the segment using the color specified in the DICOM object? yes
- how do you communicate segment semantics to the user? Developer/user can access per segment semantics (recommendedDisplayCIELab, segmentationCodeDesignator, segmentationCodeValue, segmentationCodeMeaning, segmentNumber, segmentLabel, segmentAlgorithmType) in the stack segmentationSegments object.
- **how do you support the user in defining the semantics of the object at the time segmentation is created? does not allow user to create segmentation objects. (on roadmap)
- Read task:
Test dataset | Result of rendering |
---|---|
#1 - 3D Slicer |
![]() |
#2 - 3D Slicer | ![]() |
#3 - 3D Slicer |  |
#4 - 3D Slicer |  |