-
Notifications
You must be signed in to change notification settings - Fork 41
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
Some info missing from func and fmap .json files #27
Comments
Thanks for the detailed info on this Charlotte. I'll have time to work on the active issues this week, so hopefully will have an update fixing this issue by next week. |
The "IntendedFor" issue is related to / the same as #20 |
…grated to pydicom v1.0.1 (note namespace change to pydicom).
I've just pushed v1.1.0 which fixes the IntendedFor issues (see Issue #20 closing notes). No need to include the ses-* directory name in the IntendedFor template field in the protocol translator. If you apply one fieldmap to many EPI runs, make sure to list them explicitly in the IntendedFor field, enclosed by square brackets (eg Protocol_Translator.json.txt ) The TotalReadoutTime and MultibandAccelerationFactor are handled as well as possible by dcm2niix (see for example rordenlab/dcm2niix#130 and rordenlab/dcm2niix#141). If the information required to generate these fields isn't present in the DICOM header, they'll have to be calculated and added manually as you did above in your script. Both these fields appear to be populated correctly for conversions of the CMRR MB sequence from our VE11C Prisma (eg sub-Sphere32_ses-1_task-mb6_run-01_bold.json.txt ). |
Thanks! |
Here are some info that I noticed are not in the final .json file associated with each field map and each functional run:
I wrote the following python script that all my subjects and all my run and adds all this information - in case that helps for fixing the issue within the dcm2bids.py scripts.
The text was updated successfully, but these errors were encountered: