Skip to content

Instantly share code, notes, and snippets.

@oesteban

oesteban/fieldmaps.rst

Last active April 21, 2020 14:52
Show Gist options
  • Save oesteban/21c741b55ff5d9e575f0cda9429a7264 to your computer and use it in GitHub Desktop.
Save oesteban/21c741b55ff5d9e575f0cda9429a7264 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
fieldmaps.rst

Fieldmaps table

This is the table

Priority Data Behavior
0 2+ EPIs with different PE but common IntendedFor under fmap/
  1. Estimate fieldmap (pepolar); ii) Apply fieldmap to IntendedFor targets
1 1+ EPIs with common PE and IntendedFor under fmap/ with 1+ target in IntendedFor with different PE.
  1. Estimate fieldmap (pepolar), using IntendedFor targets as alternative PEs; ii) Apply fieldmap to IntendedFor targets
2 2+ EPIs with different PE but no IntendedFor under fmap/ Expand IntendedFor to all targets and apply 0?
3 1+ EPIs with common PE and no IntendedFor under fmap/ with 1+ target with different PE. Expand IntendedFor to all targets and apply 1?
4 Targets have several different PEs
  1. Hierarchically find most granular matches for estimation (i.e., first dir-, then run-, then acq-, etc. and their combinations); ii) Expand a IntendedFor to corresponding matches
5 Fieldmap images with IntendedFor. Priority of fieldmaps: _fieldmap, _phasediff, _phase{1,2}. Apply fieldmap regularization and conversion to Hz workflow
6 No data under fmap/ and targets do not have several PEs Fieldmap-less solutions
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment