Add options to restrict region of operation about stitching HOT 2 OPEN

Hi @hinerm

I do not understand, this is done already, it always just compares a small region that is potentially overlapping. This is what in pairwise stitching the ROI is for and in the grid/collection stitching the approximate overlap.

Do misunderstand something?

Cheers,
Stephan

from stitching.

@StephanPreibisch Yes, sorry it is not clear.

What I mean is this scenario:

Suppose you have a dataset that when stitched has 30 tiles (images) per plane. If individual images are too large you may not be able to open a stitched image due to the memory limitations on individual planes. The only option right now in this case is to downsample.

However, we can't run our analyses on the downsampled pixels; we want to do so against the actual true data values.

So in this case, suppose the region we actually care about are the middle 4 tiles of tile rows 2,3 and 4. This ticket is about creating an easy way via the interface to discard the tiles outside of that region when computing overlap and fusing. Thus we end up with a full resolution, unmodified fusion of the area of interest.

If we're mistaken and there's already a way to do this, or if it still is not clear, please let me know!

Thanks,
Mark

from stitching.