[FEAT] Plain nifti <-> zarr converter #48
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.
Requires #46 to be merged first.
This PR implements a first set of "plain" format converters. Plain converters are not modality specific. Instead, they aim to convert files between file formats while attempting to preserve the data and metadata as much as possible (same data type, same axes, same spatial metadata, ...).
This PR includes a converter between nifti and [{OME|NIfTI}-]Zarr. It calls the
nifti-zarrlibrary under the hood, but also allows remote lincbrain data to be accessed, with proper authentication.For now, authentication is only used if a path of the form
dandi://...is used. I could also detect links of the formneuroglancer.lincbrain.org(as is the case in ngtools), but do not yet.It would be useful to add converters for [OME-]TIFF next. We could also quite straighforwardly implement a JP2->Zarr converter by adapting the single-slice DF converter. However, I'll wait for the zarr3 refactoring to be finished and merged before working on these.