-
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 DWI DCM TO NIFTI, b-val 0 instead of 1400, GE manufacturer #690
Comments
|
Hi Chris, to explain a bit more what we are doing, the analysis pipeline requires just the high-b volume, so there is no need to retrieve the entire series. That indeed is a trace image, which is how DWI is often used in prostate MRI analysis. It is not the intent to do the DWI analysis - we just need the reconstructed high-b scalar volume - but we were expecting that the b-value of 1400 would be parsed from the private field. If the observed behavior of dcm2niix is expected, and b-value is not supposed to be saved, please close the issue - we just wanted to report and share the sample in case there is interest to debug or alter the current behavior. |
This topic is related to issue 657, so the development branch and upcoming stable release will be more willing to create bval files for isotropic diffusion images. However, this particular series contradicts our experience with GE isotropic diffusion data. The bizarre thing about this GE dataset is that it is missing the GE private DICOM tag NumberOfDiffusionDirectionGE (0019,10E0). For an isotropic dataset, I would expect this to be You can coerce dcm2niix to create bval this series if you add two lines to the development branch of dcm2niix so it reads:
Given that this change explicitly contradicts my notes on GE diffusion scans, I am reluctant to add this change to the core dcm2niix code as it may disrupt processing of legitimate GE DTI data. The GE diffusion handling is not intuitive and as I recall can be different for product and research sequences. As an aside, when using dcm2niix, I would always suggest processing the entire series, rather than one volume for a series. This provides the tool with a better context for the data. Here you only process one volume (26 images) from the 2 volume (52 image) series. For anyone wishing to replicate this issue, the manifest for all images is:
which can be downloaded with the command:
|
@mr-jaemin thanks! These images do not report 0043,1030, so perhaps that is a more recent tag. However, they do have 0021,105a so I have used that to refine the detection of isotropic diffusion images. @ccosmin97 do you want to test the latest commit to the development branch (v1.0.20230315) and close this issue if it resolves your problem. |
I believe that the tag 0043,1030 would be one of classic private tags, not a recent tag. I found this tag from version 11 (2003) DICOM Conformance Statement. I also suspect that this tag was removed, as you mentioned for the (0019,10E0). |
I converted the same 26 slices from dcm2niix using the latest dev commit build from AppVeyor commit#c2a4b28 mentioned above. This time the correct b-value was properly saved in .bval log file. Here is the notebook for reproducibility : (dcm2niix v1.0.20230315) @neurolabusc @mr-jaemin Thank you!! I think we can close the issue. Cosmin |
Hi,
I am converting 26 slices of a DWI volume of b-value equal to 1400 to NIFTI, but the reported b-value given by dcm2niix is 0, in the .bval output file.
Here are the logs :
The DWI scan comes from QIN-Prostate-Repeatability collection:
The b-value is stored here in tag (0043,1039), and should be 1400.
As mentioned in this issue,
if b-vec values should be incorporated in tags (0019,10bb, 0019,10bc, 0019,10bd), then there might be an issue here, since these tags are present:
Reproducibility steps :
The SOPUIds of the corresponding b-val 1400 are included in mentioned google colab notebook.
Thank you!
PS : This is in the context of evaluation of SOTA prostate cancer AI models on publicly available data in Imaging Data Commons @fedorov.
The text was updated successfully, but these errors were encountered: