-
Notifications
You must be signed in to change notification settings - Fork 165
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
[ENH] Update B0Field metadata to accommodate single-blip fieldmaps #968
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not an expert: why do you remove the participant_relative
format?
Because these are strings, not paths. |
Thanks for this. |
6728d24
to
92559f8
Compare
Codecov Report
@@ Coverage Diff @@
## master #968 +/- ##
=======================================
Coverage 36.16% 36.16%
=======================================
Files 8 8
Lines 788 788
=======================================
Hits 285 285
Misses 503 503 Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Follow-up to #622. We realized that as currently worded, there are unresolvable ambiguities for pepolar schemes. Consider the case where you have two BOLD series and one reverse-PE EPI fieldmap. The inputs to estimate the fieldmap could be one or both BOLD files (along with the reverse-PE EPI), and the estimated fieldmap could then apply to one or both.
This allows files to be listed as part of multiple identifiers, and for a BOLD file to be part of an
B0FieldIdentifier
AND have aB0FieldSource
.