Import sofima's non-rigid deformation fields - #252
Merged
Conversation
Displacement field needs to open N5/zarr datasets, possibly on a cloud
# Conflicts: # pom.xml # render-app/pom.xml
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
3 participants
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.
This PR adds some functionality to import non-rigid deformation fields into render:
DisplacementFieldTransform.javaloads a deformation field base on aurl?key=value&...string. Currently, this is very tailored to ng-precomputed datasets on google cloud. A two-level cache (a static map holding oneCachedCellImgperurl?key=value&...string) is used to minimize communication and data transfer.QueryKeyValueParameters.javawas added to parse the key-value parameters of the deformation field string;N5SliceLoader.javawas modified to use that as well.ImportSofimaClient.javais used to add the non-rigid transforms to an existing stack.@trautmane Functionality-wise, this is done and tested. To be used in our current multi-sem workflow, you'll likely need to tweak
ImportSofimaClienta little bit; in particular regarding parallelization. Let me know if and how I can help with that.