Skip to content

Correcting the condition to perform the deoblique #335

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

Merged
merged 1 commit into from
Mar 10, 2023

Conversation

yasseraleman
Copy link
Contributor

The condition was always TRUE even if the values were below the specified threshold

@effigies
Copy link
Member

If I'm reading it right, any obliquity besides 0.0 was triggering the False condition and going on to be deobliqued. So this was effectively an over-stringent test. I agree with the fix; not sure if its impact will be very large. Do you have a test dataset where you can demonstrate the effect of this change?

@effigies
Copy link
Member

effigies commented Mar 9, 2023

@yasseraleman I will merge this without a test if needed, but if you have a demonstration of where this causes problems, I would appreciate it.

@effigies effigies added this to the 2.4.0 milestone Mar 9, 2023
@effigies effigies merged commit ab1b128 into nipreps:master Mar 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants