ENH: Classify vNav setter images as Navigators #13
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
I've not tested this, as I'm not sure how I can test utility gears locally. The idea is to classify volumetric navigator scans as Navigators.
The ABCD project, HCP Lifespan, and others use 3D navigators to prospectively correct motion during T1w and T2w scans. The navigators themselves, the "setter" images, are low-resolution EPI images used to track motion. An example series description might be "ABCD_T1w_MPR_vNav_setter", which consists of multiple low-resolution EPI images. Because of "T1" in the name, these get classified as T1, resulting in many extra NIFTI files and causing problem for gear rules targeting actual T1w images.