Add static utility class for scripting API #59
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.
I've been using this utility class
StitchingUtils
for a while now, e.g. when I need to stitch multi-series images that are not being read correctly via Bio-Formats, or for images that are loaded into memory already in scripting workflows, to avoid writing new files and relying on aTileConfiguration.txt
file.This adds the following static methods:
computeStitching(images, positions, dimensionality, computeOverlap)
returning the translation models for each tile,as well as:
fuseTiles(images, models, dimensionality, fusionType)
andfuseTiles(images, models, dimensionality)
performing the actual fusion (with blending being the default fusion method).As there seems to be some community interest in having more accessible stitching API (e.g. in the discussion of imagej/pyimagej#35), I thought it might make sense to migrate these utility methods upstream from
faim-ij2-visiview-processing
into this repository.@StephanPreibisch, @ctrueden let me know what you think.