-
Hi everyone, @MMelQin @gigony @GreySeaWolf I'm trying to create a toy image registration sample using the app-sdk + niftireg using some MR modality images and I'm having some issues that I would like to share with you and get your thoughts. It seems like DICOMSeriesToVolumeOperator fails to complete due to the absense of Rescale Intercept attribute. I am used to work with CT modality (in which this DICOM tag is conditionally required), so I am not sure if this is a problem with the DICOM series (although I think the series is OK as I am able to open it in a viewer like Aliza). I'm attaching a .zip containing a notebook with the steps to reproduce the error. 01_toy_registration_sample.zip Thank you! Error output:
I get this error:
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Thank you @macayaven Carlos for your feedback and question. Yes, I did encounter the exact error, and had created a bug more than a month ago, but somehow, did not get to fix it in time for the App SDK v0.2 release. Will schedule this bug for v0.3, the latest. For sure, the DICOM series in not to blame. When the intercept and/or slope are not present, it is safe for the processor to use the defaults, namely 0 for intercept and 1 for slope respectively. Thanks also for mentioning Aliza. Some of the working group members are using it, too. Outside of the commercial products, I typically use 3D Slicer, MicromDicom, and sometimes Orthanc (its viewer is really limited but parser is good). The bug has been fixed in #236 |
Beta Was this translation helpful? Give feedback.
Thank you @macayaven Carlos for your feedback and question.
Yes, I did encounter the exact error, and had created a bug more than a month ago, but somehow, did not get to fix it in time for the App SDK v0.2 release. Will schedule this bug for v0.3, the latest.
For sure, the DICOM series in not to blame. When the intercept and/or slope are not present, it is safe for the processor to use the defaults, namely 0 for intercept and 1 for slope respectively.
Thanks also for mentioning Aliza. Some of the working group members are using it, too. Outside of the commercial products, I typically use 3D Slicer, MicromDicom, and sometimes Orthanc (its viewer is really limited but parser is good).
The…