-
Notifications
You must be signed in to change notification settings - Fork 228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dcm2niix generates one .nii per direction with Siemens Magnetom Sola DWI data #383
Comments
I think you have diagnosed the issue correctly. The Series instance UID should be shared by all images of the series. You can use the merge command ( I have never seen DICOM data from a Sola before, but it appears to use the same XA10/XA11 software as the Vida. You should be aware that the XA series generates DICOM images that are radically different than any previous Siemens scanner. Please see my comments regarding using the Anonymization and Mosaic features on this generation of scanners. In brief, if you use the console to anonymize or save as mosaic, the resulting images no longer have the information required for subsequent analysis. This reflects a limitation of the DICOM images, not my software. For non-XA systems (e.g. Trio, Prisma, Skyra) saving EPI volumes as mosaics results in less disk usage and fewer DICOM files. Therefore, Siemens users are in the habit of selecting mosaic images. This strategy will cause data loss if applied to the XA series. Feel free to send a sample via DropBox/GoogleDrive to email address shown in my avatar. However, if your XA data is saved as mosaics or as Siemens anonymized there will be no way to salvage important parameters. |
Hi, Thanks for answering so quickly. Thanks again, Pauline |
@PaulineRoca can you use a tool like dcmdump or Horos to read the DICOM header and tell me if the
If so, this is related to issues 275 and 296. Specifically, a user applied Matlab's dicomanon to the data scrambling the crucial SeriesInstanceUID (0020,000e) and likely wiping out a lot of other crucial information. I do not have much experience with Siemens XA data, but for other Siemens MR data this tool removes the crucial CSA header, wiping out many details including NumberOfMosaics, SliceNormalVector, DiffusionGradientDirection, SliceMeasurementDuration, BandwidthPerPixelPhaseEncode, PhaseEncodingDirectionPositive, ASL settings, etc. If this is the case for you, the issue is not with my software, but the crude anonymization applied. While anonymizing DICOM data is important for data sharing, one needs to take care that the anonymization tool preserves the critical sequence details. I have been impressed with gdcmanon. I have updated a great and desperate kludge to my software, whereby if Matlab DICOMANON is detected it will use the Series Date and Series time in place of the SeriesInstanceUID. One would think that series date/time would be identify an individual better than the UID, but for some reason DICOMANON preserves these values. This kludge may stack your series correctly, but I would heed the warning that is generated that these images are likely to be severely impoverished. Even basic DICOM viewers like HOROS will see each slice as a separate series. These images are not archival. If you have a license to Matlab you should contact them to repair their software to prevent such data loss. Images corrupted by dicomanon are not archival quality. If you want to try out my great and desperate kludge, you can get the development release: On MacOS and Linux you can build the developmental branch with these commands:
Windows users should be able to get a compiled version from AppVeyor. |
* tag 'v1.0.20200331': (52 commits) Update submodules Update dcm_qa submodule. UIH 3D sequence quirk New release, EstimatedTotalReadoutTime/EstimatedEffectiveEchoSpacing (rordenlab#377) Philips TotalReadoutTime (rordenlab#377) Cleanup Experimental Canon DICOM support (rordenlab#388) Experimental solution for issue 384 (rordenlab#384) Detect catastrophic anonymization (rordenlab#383) Only report "multiple inversion times" if 0018,9079 values differ (e.g. Bangalore data in https://github.com/neurolabusc/dcm_qa_philips) Consistent echo naming (rordenlab#381) Philips partial Fourier (rordenlab#377) Support InversionTImes (0018,9079) tag (rordenlab#380) Philips effective echo spacing formula ambiguous (rordenlab#377) TR for Philips 3D EPI (rordenlab#369) Citation (rordenlab#102) GE PET with variable slice intensity (rordenlab#374) Estimate Philips EffectiveEchoSpacing (nipreps/sdcflows#5) GE slice interpolation (rordenlab#373) 3D EPI TR (rordenlab#369) 3D phase (rordenlab#371) Enhanced ordering (rordenlab#372 (comment)) ...
Hi,
I tried to convert DWI data from a Siemens Magnetom Sola MR scanner but I obtained one output nifti file per direction and dcm2niix crashes before the end.
Command:
Output images:
The error log is at the end of this issue.
I looked at the DICOM tag, and there is one different SeriesInstanceUID (0020,000E) for each diffusion volume (one per direction of the diffusion gradient) whereas all the DICOM files share the same Series Number (0020,0011).
Do you have any idea about the pb ?
Thanks in advance !
Pauline
Error log
The text was updated successfully, but these errors were encountered: