Hi all, I've been working with a collaborator who wants to use MITK to load some oblique DICOM images, and we're coming across some weirdness. Below is a link to that zipped data as well as two error screenshots - one when attempting to load the saved NIfTI segmentation in ITK-Snap (which seems more helpful), the other from trying to load DICOM-Seg (probably less helpful). https://www.dropbox.com/s/0z6bprrcjpswwv4/mitk-itk-snap-oddness.zip?dl=0
When we load this data up in MITK Workbench 2021.02, my coworker gets two items in the Data Manager, and I only get one (this is bizarre to me, but is secondary in importance to the next thing). Further, if I create a segmentation on that image using the Multilabel Segmentation plugin and save it, it won't load up alongside the original DICOM in other software like ITK-SNAP. Looking at the image info, it seems like MITK loads this image in as a 512x532x32 image, whereas (for example) ITK-SNAP and Slicer load it up as 512x512x32. Then this is getting propagated to the segmentation when it's created. Can someone help point me in the right direction as to what's going on here? Is this something wrong with the DICOM itself? I am still pretty new to all the details about DICOM versus NIfTI loading/viewing, but none of this seems to happen with non-oblique images. Alternatively, if anyone's experienced this and knows of a workaround, that would be good too. Thanks! Alex Getka
_______________________________________________ mitk-users mailing list mitk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mitk-users
