Description
Describe the bug
It was observed that the DICOM Seg instance from DICOMSegmentationWriterOperator now has multiple seg slices on the same frame, i.e. multiple segmentation slices each should be overlaid with the referenced original DICOM instance (image slice) are now jammed onto the same frame, like an array of thumbnails, as seen in the screenshot.
This issure has been reproduced in App SDK main, tag 0.1.1, and 0.2, so the changes within PR #238 are not the cause of the errors. It is further noted that the DICOMSegmentationWriterOperator had been tested working properly in release v0.2, except a known issue with a specific input data set.
The generated DICOM Seg instance has been tried on MicroDICOM and Aliza, with the same display issue.
It is unknown what the root cause is as of now.
Steps/Code to reproduce bug
Run the example Spleen app
Get the DICOM Seg output
Load the DICOM Seg instance with MicroDICOM or Aliza (both are freeware)
Expected behavior
Segment(s), which is single in the Spleen app but multiple in the UNETR app, on a specific slice (referring to a specific DICOM instance/image at a given position), is expected to be on its own frame, so that when both DICOM Seg and original DICOM series is loaded together in the viewer, the segment(s) can be shown overlaid on the original slice/image in the DICOM series.
Environment details (please complete the following information)
- OS/Platform: Ubuntu 18.04 LTS
- Python Version: 3.7
- Method of MONAI Deploy App SDK install: source
- SDK Version: main in dev mode
Additional context
Puzzling as the DICOM Seg writer was tested working correctly, but now, even earlier tagged versions have the issues, at least in dev env.