That goes with the lung dataset) that can be read back into Horos. Region (2D/3D Segmentation) and save it as a. I can create a segmentation using the 2D viewer menu ROI. Import a single segmentation file, nothing seems to happen. Stack, I only see the image stack in the database, and even if I explicitly If I import a directory with both segmentation(s) and a corresponding image
Single-DICOM-file segmentations seem to be ignored
There are many other nuclear medicine workstations that use the same interpolation as IntelliSpace: Mirage (Segami), Xeleris (GE), Syngo (Siemens), etc. Both are from the same slice of the same study, using the same CLUT and WL/WW settings as shown at the right side of each image. The second image was captured from Philips IntelliSpace, a Windows-based radiology and nuclear medicine workstation. The first image was captured from Horos (v3.1.2) using Lanczos 5. Here is an example of this issue in an axial slice of a brain FDG-PET study. And it gets worse when using multiple color CLUTs, which are very useful in nuclear medicine. However, it becomes evident in NM and PET images, which use 256 x 256 or even smaller matrices. This may not be an issue with grayscale and large matrices, like in CR, CT or MRI. It results in noisy images where individual pixels still can be seen, even with the "High Quality Zoom (Lanczos 5)" option. I have noticed that the interpolation method used in Horos is different from that of other DICOM workstations.