Cannot import AIM contour collections for NM Sessions, cannot export AIM contour for some NM Sessions

Mo Alsad

348217: the images of this session have an DERIVED\SECONDARY image type which may indicate that the slices of each image set were combined from individual NM images. The AIM IO handler requires a unique Instant Number (& SOPInstanceUID) in order to map the contour polygons to the relevant slice. Since each image has a multiframe slices sharing the same Instance Number and SOPInstanceUID values, the AIM IO handler has no way to determine which slice to use for contour mapping and rendering. That is why nothing is displayed on the images upon importing the ROI collection. Exporting does not show errors, but the contours can be assigned a wrong slice number. For instance, say that we draw contours on the second frame for an image with instance number = 1, they will be associated with the first frame since the instance number is the same for both slices.

352602: in the Contours panel, it is the expected behaviour to show only the contour ROI list corresponding to the active scan. The confusion arises here due to the scan number which is the same for all scans. We used to display the SOPInstanceUID along the scan number, but it visually clutters the UI. We are considering appending a suffix to the displayed scan number (e.g. a sequence of a, b, c …) which when hoovered over with mouse reads the SOPInstanceUID value.

2022-02-15T20:30:44+00:00

Comments (4)

Z-Kate Alpert Account Deactivated reporter
- edited description
- 2022-02-09T23:07:02+00:00
Mo Alsad
348217: the images of this session have an DERIVED\SECONDARY image type which may indicate that the slices of each image set were combined from individual NM images. The AIM IO handler requires a unique Instant Number (& SOPInstanceUID) in order to map the contour polygons to the relevant slice. Since each image has a multiframe slices sharing the same Instance Number and SOPInstanceUID values, the AIM IO handler has no way to determine which slice to use for contour mapping and rendering. That is why nothing is displayed on the images upon importing the ROI collection. Exporting does not show errors, but the contours can be assigned a wrong slice number. For instance, say that we draw contours on the second frame for an image with instance number = 1, they will be associated with the first frame since the instance number is the same for both slices.

352602: in the Contours panel, it is the expected behaviour to show only the contour ROI list corresponding to the active scan. The confusion arises here due to the scan number which is the same for all scans. We used to display the SOPInstanceUID along the scan number, but it visually clutters the UI. We are considering appending a suffix to the displayed scan number (e.g. a sequence of a, b, c …) which when hoovered over with mouse reads the SOPInstanceUID value.
- 2022-02-15T20:30:44+00:00
Mo Alsad
The issues should have been fixed now in the dev branch 3.3.0-SNAPSHOT.
- 2022-03-07T20:44:18+00:00
Mo Alsad
- changed status to resolved
- 2022-03-22T11:56:08+00:00
Log in to comment