-
Notifications
You must be signed in to change notification settings - Fork 264
WIP: parrec2nii sets qform code to 2 #478
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
WIP: parrec2nii sets qform code to 2 #478
Conversation
We've added two tests; the first, a unit test, that requires the |
Thanks for doing this. Would you mind posting to the mailing list to ask for opinions about relying on the 'mock' library? |
Thanks. Would you mind adding mock to the |
Drop numpy check as we already require numpy >= 1.5.
I added a check for "mock" when running tests via |
RF: check for "mock' module when running tests
…nibabel into qform-provided-then-qform-code-2
Use the machinery in |
I completely overlooked that.. but the downside of that scriptrunner is that we still wouldn't be able to test the separate functions / import the code. Long term I think ideally we'd refactor most of the logic out of the |
Current coverage is 93.81% (diff: 51.26%)@@ master #478 diff @@
==========================================
Files 161 163 +2
Lines 21321 21555 +234
Methods 0 0
Messages 0 0
Branches 2284 2315 +31
==========================================
+ Hits 20100 20221 +121
- Misses 801 902 +101
- Partials 420 432 +12
|
How about JasperVanDenBosch#2 ? |
Move the parrec2nii code into its own module for easier testing.
RF: move parrec2nii code into own module
Looks good, thanks! I'll check back if there's any failing tests. |
Thanks. I think coverage is down quite a bit, but I believe that's because the parrec2nii command code wasn't covered well, and we are now seeing that in the coverage report, so no not the fault of this PR. Current PR is fine with me. Any other suggestions? |
No further suggestions! Thanks On Aug 11, 2016 2:49 PM, "Matthew Brett" [email protected] wrote:
|
Actually, sorry, now I think if it - shouldn't the |
hi matthew, because we are dealing with un-transformed data (pre-alignment with standard brains etc), both the q and sforms (and codes) should be the same whichever is decided. as i understand it, sform is diverged from qform when transformed into standard space and qform is kept to reference path to original subj space. see |
qform / sform code of 1 is fine with me, but it is a small API break. If there is some software that behaves differently with sform codes of 1 and 2 then something would change, but I doubt that would happen. OK to take the risk? |
I am fine with setting both to 1. (The previous behavior was sform=2, qform=0?) |
Right |
OK - I'll merge this as-is, then do a PR for the code changes. |
As discussed in nipy#478
fixes #463