-
Notifications
You must be signed in to change notification settings - Fork 21
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
Iss169 #173
base: master
Are you sure you want to change the base?
Conversation
…der has already been parsed.
…is done at the level of NIAK_READ_MINC and NIAK_READ_NIFTI). Code is cleaner that way.
@pbellec What is the statue of this old pull request? Should I work on it to have it merge, or we just close it. Its old and full of conflicts. |
I have automatically resolved conflicts ("theirs") and, after review, I think all the changes I made are in there. It's not a critical PR, but it adds a nice feature and cleans up a bit the code of the reader/writer, so I'd like to push it through. I don't think it should break our tests ... fingers crossed. |
very weird... the scores tests fail ?!? will have a look :/ |
This PR should fix issue #169 Although the added feature is minor, I have refactored a bit the reader/writer. There is now a separate function
niak_read_data_minc
to read the data array in a minc file, provided a header structure is available. Also the un(g)zipping of file is now handled by a generic functionniak_unzip
. The feature is available for both minc and nifti (niak_read_data_nifti
andniak_read_data_minc
), and the other functions (niak_read_minc
,niak_read_nifti
,niak_read_vol
) now depend on these functions.