-
Notifications
You must be signed in to change notification settings - Fork 52
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
Consider renaming StructuralReference
interface
#612
Comments
I think we should upstream the fix directly into |
Sounds good, a just one comment:
BTW, we should be careful that these tweaks work well with MapNodes. I just discovered that this tweak - niworkflows/niworkflows/interfaces/fixes.py Lines 87 to 133 in e2a86a4
|
So outputs["short_circuit"] = self.inputs.short_circuit and len(self.inputs.in_files) == 1 I feel like I would rather not use the same name for two subtly different concepts, but as long as I understand what you want, we can quibble about naming when we go to implement. |
Coming out from #610 (comment)
Although, I'm still not sure
StructuralReference
is a bad name. We are indeed calculating "structural" images (as in, with the maximal structural contrast as possible).If that argument is convincing, we could close this.
The text was updated successfully, but these errors were encountered: