Repository navigation
feat: support rgb nifti - #15
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
partial fixes #13
nibabel reading rgb nifti does not read the dataarray as [x, y, z, 3] numpy array, but instead as [x, y, z] numpy array, with datatype as
[(R, dtype), (G, dtype), (B, dtype)].This breaks the built in datatype check of neuroglancer-scripts.
This PR checks for this datatype, and patches the necessary parameters:
info_fullres.json, adds an additional dimension, sonum_channelis correctly set to 3.reshapemethod, but with.view-> slice manually, which seems to be faster)Admittedly, the second approach is very naive. I would welcome any feedbacks on doing it more efficiently.