-
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
No slice-timing JSON output with Siemens scanner #309
Comments
Your data was acquired with A25 software circa 2004 ( While the Allegra provided state-of-the-art hardware for its day, it saw limited production, so the software saw less development than for the Trio (which at least initially had inferior gradients). I think it is very unlikely, but it is possible that slice timing was back-ported to Allegra's that were unable to upgrade with the contemporary Trios. One way to check the contents of the your CSA header is to run dcm2niix with logorrheic verbosity ("-v 2"). You might want to convert just a single volume of your EPI data with this mode, as the output can be overwhelming. This would reveal both the presence of a CSA header (0029,1009) and within the header it would reveal a field "MosaicRefAcqTimes":
|
Thanks for the quick reply. It's apparently not there :'(
|
dicm2nii uses additional methods to determine Siemens Slice Timing |
If you compile from the developmental branch, dcm2niix now clones dicm2nii's method for extracting slice times from ucMode. I would be grateful if you could test this thoroughly: I only have access to a single Siemens B12 dataset for testing. If you have access to this system, it would terrific to have a validation dataset acquired (e.g. just a few volumes each of a low resolution fMRI sequence acquired with ascending, descending and interleaved slice order). I would also be interested in seeing a dataset where the mosaic slice order is set to H>>F. While this is an extremely rare setting, I am not precisely sure if my current solution handles the spatial transform correctly. |
Thanks a lot for taking the time to work of this. I have very limited access to our MRI system but i'll ask if the person in charge could create that validation dataset.
|
You are not running the developmental branch version - it will report v1.0.20190707 instead of v1.0.20190410. On Unix systems, you can build the developmental branch with these commands:
This will create a new executable in the folder /dcm2niix/build/bin. You can copy this to your path if you want to use this version exclusively. |
I indeed forgot the --branch term so i was working with the master in a folder named development...
|
Can you send me a few volumes - send a dropbox invitation to my email (shown in my avatar). I was able to test the code on B12 but have no examples of A25. |
Just sent you a box link. |
Last development worked ! Thanks a lot for making those changes in such a short time! |
I added examples from B12 and B13 that do not include "MosaicRefAcqTimes" but where one can infer slice times from "sSliceArray.ucMode". If you have sample datasts (e.g. phantoms) that you can share from your A-series equipment, it would be great to include them. It is hard to feel confident that this is a robust solution. Test extensively and report any unusual behavior. |
* tag 'v1.0.20190720': Update dcm_qa submodule. Handle rare VRs (https://www.aliza-dicom-viewer.com/download/datasets) New default merge option "-m o" will merge CTs and segment MRIs (https://discourse.slicer.org/t/odd-dicom-import/7576) --progress option (rordenlab#314; rordenlab#312) Tune verbosity (rordenlab#312) GE Slice Timing From Protocol Data Block (rordenlab#311) Desparate guess of GE slice times from ProtocolDataBlock (clone dicm2nii, assumes TA close to TR) Support interleaved (rordenlab#309) Slice times from ucMode (rordenlab#309) GE number of slice discrepancy (rordenlab#306) Simplify slice timing code, develop stc validation (https://github.com/neurolabusc/dcm_qa_stc) hdr.vox_offset is a float not integer (https://www.nitrc.org/forum/message.php?msg_id=27155) BIDS tags for PASL fairest sequent Read 0019,1029 (rordenlab#296) Generate warning rather than error when palette colors are detected (UNFmontreal/Dcm2Bids#54) Update tinydir call (rordenlab#298) Bruker 4D datasets: correct slice ordering Bruker 4D datasets: Fix parametric maps grouping Changes up to divest v0.8.1 Support isotropic scans for NRRD
This is the output given by DCM2niix.
The text was updated successfully, but these errors were encountered: