-
Notifications
You must be signed in to change notification settings - Fork 272
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
Changed behavior of applywarp, flirt, and bet in FSL 6.0+ #118
Comments
While we are at it, we should also make sure that all |
To me, that reads only as "here is a way to work around it", while not saying anything about whether or not they are inclined to make it behave as in fsl5. There is no useful unique data that can be put in the extra frames, and this would be a very weird and unexpected place/method to specify effectively a repmat (and can very easily break scripts written under fsl5, and I very much doubt they want to break people's scripts). This deserves followup with FSL, and could merit a bugfix release by itself. |
flirt aborting when the reference isn't a single frame sounds like a very silly change, but less likely to be accidental. Maybe it was a quick hack to prevent the extra-frames behavior we see in applywarp without rewriting the resampling code to actually fix the issue? We should get the whole story from the FSL people, and tell them what we think about the new behavior. |
A note regarding how the behavior of FSL5
FSL6
|
FSL 6.0+ apparently expects that the
-r
(reference) volume will be a single 3D volume in any call toapplywarp
within FSL 6.0+.https://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind1811&L=FSL&D=0&P=74472
To me this change in behavior should be considered a bug, but based on the list-serve response above, FSL doesn't appear to consider it to be a bug. So, we need to review all our
applywarp
calls across the entire code base, and ensure that the-r
volume is a single 3D volume in all cases.The text was updated successfully, but these errors were encountered: