-
Notifications
You must be signed in to change notification settings - Fork 298
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
default output grid: BOLD or template grid? #2060
Comments
Yes, your interpretation is correct. We'll look into this and come back to you ASAP. |
I'm not seeing that exact behavior, although I'm using the cutting edge development version:
@mgxd, do you have any ideas of when we might have addressed this issue? |
interesting - i'm also running the cutting edge version (with nipreps/niworkflows#492 applied) and I see the same problem as @snastase
input BOLD files:
|
@snastase - specifying your outputs explicitly with |
Excellent—thanks! |
My understanding according to the documentation is that specifying, e.g.,
--output-spaces MNI152NLin2009cAsym
without a:res
will by default output the BOLD data in the native BOLD grid (synonymous to:res-native
; this is what I want). However, running version 20.0.2 seems to yield preprocessed outputs in the 2 x 2 x 2 mm template grid rather than the original 3 x 3 x 4 BOLD grid. My fMRIPrep invocation is:Here's a screencap of

nib-ls
output where you can see that the preprocessed BOLD outputs in BOLD and T1w spaces (--output-spaces anat func
) are in the original 3 x 3 x 4 BOLD resolution, where as the outputs in MNI space (--output-spaces MNI152NLin2009cAsym MNI152NLin6Asym
) have inherited the 2 x 2 x 2 template grid (despite me not specifying:res-2
).Maybe this is the correct behavior and I'm just confused about the documentation...? I can try re-running with explicitly specifying
:res-native
and see if that displays the correct behavior.The text was updated successfully, but these errors were encountered: