-
Notifications
You must be signed in to change notification settings - Fork 229
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
v1.0.20230411 removes legitimate b=0 volumes in GE DWI scan after flagging them as "ADC or trace images" #777
Comments
Please share a sample with my institutional email. |
This issue was associated with code change with issue #690, trying to detect GE non-DTI based on For GE DTI, Additionally, the issue was associated with old multi-shell data (prior to 29.1) where b=0 images (as a part of diffusion tensor file) was incorrectly labeled in DICOM (bval > 0, bvec = all 0). As noted above, MR30.1 data doesn't cause this issue. The PR also address (or remove) the following warning:
For #359, I limited the warning with GE non-diffusion (i.e fMRI) only @psadil Once the PR is merged by @neurolabusc, please test your data and close the issue if it works. |
@mr-jaemin , thanks for the fix! 2a515f5 seems like it'll work for our data. Looking forward to the pull request making it into a dcm2niix release. |
The dev. version v1.0.20240117 would address the issue. @psadil please try the dev version and close this if resolved. |
Looks good, thank you |
* tag 'v1.0.20240202': (135 commits) Update submodules Refactor (rordenlab#791) gantry tilt tolerance (rordenlab#791) GE step description (rordenlab#790) PatientOrient -> Patient Position (rordenlab#786) Prevent shell expansion (rordenlab#789) Replace presumably accidental bitwise AND operations Update JasPer API calls for compatibility with newer versions of the library Update divest logic, reducing duplication and supporting new mode of operation Fix PhaseEncodingDirectionDisplayed for GE Update date GE Diffusion issue rordenlab#777 minor GE Diffusion issue rordenlab#777 Kludge for issue 775 (rordenlab#775) add docstrings better python wrapper I/O issue 769: Mildly relax the check for bvec components > 1. PRs (rordenlab#745; rordenlab#768) Edge cases (rordenlab#763, rordenlab#749) Code spell ...
Describe the bug
Given a diffusion scan collected on a GE scanner, the newest version of
dcm2niix
removes legitimate b=0 volumes as "ADC or trace images".These are the volumes that are removed
To reproduce
If it'll help, the data can be shared.
FWIW, the software on the scanner that collected these data has recently been upgraded from "28\LX\MR Software release:RX28.0_R04_UHP3T_2111.a" to "30\LX\SIGNA_LX1.MR30.1_R01_2322.c", and new scans do not have volumes flagged and removed.edit: please ignore, the information about an upgrade was a miscommunication.Expected behavior
A clear and concise description of what you expected to happen.
Output log
v1.0.20220720 (desired behavior)
Note, I don't know which volumes are triggering the "Some images had bval>0 but bvec=0" warning. According to the produced bvals/bvecs files, there are no such volumes.
v1.0.20230411 (unexpected behavior)
Version
Please report the complete version string:
Troubleshooting
Please try the following steps to resolve your issue:
The text was updated successfully, but these errors were encountered: