Skip to content
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

Compare pixel array parsing results with dcm2niix #70

Open
ZviBaratz opened this issue Oct 19, 2021 · 2 comments
Open

Compare pixel array parsing results with dcm2niix #70

ZviBaratz opened this issue Oct 19, 2021 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@ZviBaratz
Copy link
Collaborator

@matthew-brett will test against dcm-qa to find differences in parsing results.

@ZviBaratz ZviBaratz added the enhancement New feature or request label Oct 19, 2021
@ZviBaratz ZviBaratz added this to the v1.2.0 milestone Oct 19, 2021
@ZviBaratz ZviBaratz modified the milestones: v1.3.0, NIfTI Conversion Feb 28, 2022
@ZviBaratz ZviBaratz removed this from the NIfTI Conversion milestone Feb 28, 2022
@neurolabusc
Copy link

@ZviBaratz not sure why this got assigned to me. You can add any dcm_qa tests as submodules and use AppVeyor or Travis to test - see dcm2niix for examples. Since dcm_qa always saves uncompressed NIfTI data (as different GZ compression levels/libraries lead to file differences), you can always check the pixel array with a simple shell script using a terminal command like cmp -i 352 A.nii B.nii and checking the return value, though you could do this in Python as well.

@ZviBaratz
Copy link
Collaborator Author

@neurolabusc thanks for the guidance! My mistake regrading assignment, I was playing around with the new project boards and somehow that happened.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

No branches or pull requests

3 participants