You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the --bind-fmaps flag populates the IntendedFor fields in the fmap/*.json files with the fieldmap(s) closest in time to the start of each BOLD series.
Because our fieldmaps are collected at the end of each BOLD run (and named accordingly), it would be nice to add some flexibility to the bind-fmaps feature. For example:
an option to populate IntendedFor with the fieldmap closest in time to the end of the BOLD series
and, if possible, an option to populate the IntendedFor fields with the fieldmaps indicated in Protocol_Translator.json
Thank you for your help!
The text was updated successfully, but these errors were encountered:
Currently, the --bind-fmaps flag populates the IntendedFor fields in the fmap/*.json files with the fieldmap(s) closest in time to the start of each BOLD series.
Because our fieldmaps are collected at the end of each BOLD run (and named accordingly), it would be nice to add some flexibility to the bind-fmaps feature. For example:
Thank you for your help!
The text was updated successfully, but these errors were encountered: