Skip to content
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

Mosaic #550

Closed
rhedouin opened this issue Oct 6, 2021 · 3 comments
Closed

Mosaic #550

rhedouin opened this issue Oct 6, 2021 · 3 comments

Comments

@rhedouin
Copy link

rhedouin commented Oct 6, 2021

Hello,
I have a problem [issue #369 about mosaic image], (I also posted there before to see that it was closed, sorry for the duplicate). I tried your solution (go to the development branch) but it doesn't work in my case. I still have the following warning

Warning: Assuming icon SQ 07a3,10ce.
Unsupported overlay origin 0/0
Warning: 0008,0008=MOSAIC but number of slices not specified: controls_Tours_cusp_dicom_1/ACTIDEP-03011_1.4.9.12.34.1.8527.2207176245825200820373228239247760676011.dcm

If I understand correctly your answer, dcm2niix guess that the mosaic is 7x7 images ? In my case it's 9x9.
I'm also not sure what the unsupported overlay origin means never.

Thanks for any help you could afford.
Best,
Renaud

@neurolabusc
Copy link
Collaborator

Can you provide some context - is this data from the ADNI dataset? Feel free to send me an example DICOM image by sending a link to my email (shown in my avatar). I suspect that these DICOM images were corrupted either by the insertion of a image icon or an anonymization tool that stripped out the CSA header.

@neurolabusc
Copy link
Collaborator

neurolabusc commented Oct 6, 2021

Thanks for the example images. I think you want to check the provenance of these images, and convert copies prior to their corruption. These are limitations in your DICOM data, not dcm2niix. Here are some of the limitations of your DICOM images:

  1. The CSA header has been removed, beyond revealing the number of slices in a mosaic, this structure also stores the diffusion gradient vectors which will be required to analyze these diffusion images.
  2. Icons have been inserted into these images. This increases file size and often cause issues. I was surprised that these refer to Elscint which merged in 1998.
  3. I notice that these images were touched by a dcm4che PACS system. I would be wary of this, as these tools can obfuscate DICOM (which is already a complicated standard), disrupting popular tools.
  4. The images were acquired as a 9x9 mosaic. I assume the original images were saved as 990 rows and 990 columns, but the data has been reformatted to 992 columns. Presumably, some tool padded the columns to make them evenly divisible by 8. However, 992 is not evenly divisible by 9. This explains why dcm2niix refuses to de-mosaic the data.
(6000,0010) US 990                                      #   2, 1 OverlayRows
(6000,0011) US 992                                      #   2, 1 OverlayColumns
(0018,1310) US 110\0\0\110                              #   8, 4 AcquisitionMatrix

@rhedouin
Copy link
Author

rhedouin commented Oct 7, 2021 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants