-
Notifications
You must be signed in to change notification settings - Fork 126
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
Issue with echo times from dual-echo field maps #789
Comments
Thanks @levchenkoegor for the bug report! Is there a sample of DICOM files you might be willing to share?
checkout this ReproNim/reproin#18 (comment) -- may be you could just remap into reproin, and if we fix this fieldmap issue -- should might be the easiest way. |
Hey @yarikoptic! Thank you for your response! Sure! Please find attached the archive with DICOMs. |
I've been reading the code and have a feeling that the problem appears here: Line 355 in 4c2c2c0
When one DICOM is treated as the same as the other one based on is_same_series() method. Probably the TE isn't taken into account when two DICOMs are compared. |
didn't look myself yet -- did you figure it out @levchenkoegor ? |
@yarikoptic not really, unfortunately couldn't specify exactly where the problem actually occurs |
Summary
I am converting my raw data to BIDS format. I’m encountering an issue with HeuDiConv during the conversion of field maps, and I suspect it has to do with how the tool groups sequences into the CSV file during the conversion process.
I am using dcm2niix within HeuDiConv to convert raw DICOM files into BIDS format. The dataset includes dual-echo GRE field mapping sequences with two echo times. dcm2niix correctly generates the nifti files and associated JSON sidecars, with accurate metadata:
If I check the echo times in JSON files it correctly shows 0.01 sec, 0.01246 sec and 0.01246 sec respectively for _e1, _e2 and _e2_ph files.
However, when HeuDiConv generates the TSV file that groups the sequences, it seems to misinterpret or incorrectly group the echoes, resulting in misleading or duplicated entries for the field map sequences. Here is the part of the TSV file:
<style> </style>As you can see there is definitely a problem: there is only two field_mapping protocols with the same TE (there should be three and two of them with different TE).
I am running HeuDiConv using docker on our lab server:
I plan to use the heuristic.py file later to organise the data in BIDS-valid format, but if the grouping is done wrong at the first step it seems hard to find a solution.
I am wondering if:
Any help or insights would be greatly appreciated! I’d be happy to provide more details if needed.
Thanks in advance!
Platform details:
Choose one:
The text was updated successfully, but these errors were encountered: