-
Notifications
You must be signed in to change notification settings - Fork 532
fsl.FNIRT does not generate fieldcoeff_file when it is an output connection #2102
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
Comments
@mwaskom looks like there is no default value for |
So remind me, to fix this I need to add |
If |
By "can always be created" you mean can be created by an interface with only the mandatory inputs set? How is the suffix determined with |
Yes, that's a better way to say it 👍
By setting |
@mwaskom is this all set? |
No, it needs a PR, I just haven't had time for it. |
i did like to help |
Uh oh!
There was an error while loading. Please reload this page.
Summary
When using
fsl.FNIRT
you have to setfieldcoeff_file=True
in the inputs even when thefieldcoeff_file
output is connected to a downstream node.Actual behavior
No
fieldcoeff_file
is written and the downstream node errors out.Expected behavior
Shouldn't there be an association between the input and output traits
fieldcoeff_file
be written with a default filename and passed to the downstream node? It's been so long that I've dealt with theInterface
guts that I forget how this works ...The text was updated successfully, but these errors were encountered: