PreibischLab / BigStitcher

ImgLib2/BDV implementation of Stitching for large datasets
GNU General Public License v2.0
64 stars 14 forks source link

`Preserve original anisotropy` option disappeared from Fusion menu #100

Open nvladimus opened 2 years ago

nvladimus commented 2 years ago

Hi, I noticed that Preserve original anisotropy checkbox is now missing from the image fusion menu, so BigStitcher forces the user to re-sample z-planes and make the voxel isotropic. This was actually a very useful option, sometimes it is necessary to preserve the original image dimensions. Is this option now hidden, or discontinued altogether? Thanks!

StephanPreibisch commented 2 years ago

Hi, this happens if the x/y calibration is not identical ... might this be the case?

nvladimus commented 2 years ago

Hi, no, here are my xml file parameters:

        <size>2048 2048 1179</size>
        <voxelSize>
          <unit>um</unit>
          <size>6.55 6.55 5.0</size>
        </voxelSize>
...
<ViewTransform type="affine">
        <Name>calibration</Name>
        <affine>1.0 0.0 0.0 0.0 0.0 1.0 0.0 0.0 0.0 0.0 0.7633587786259542 0.0</affine>
      </ViewTransform>

I assume that the voxel size is in xyz order.

nvladimus commented 2 years ago

Hi, @StephanPreibisch, I double-checked the voxel sizes in various datasets - this is not the case. The latest version of BigStitcher always resamples the stack during fusion to make the voxel isotropic. Here is my (small) example dataset: https://drive.switch.ch/index.php/s/9dvaYHprSUhUZbK When fusing, XY dimensions (15um/px) are blown up to match the Z step size (6 um). When XY dimensions are smaller than Z-step, the number of planes is blown up. Any help is much appreciated!

StephanPreibisch commented 2 years ago

Hi, you have the uncommon case that the z resolution is higher than XY. I could remove the condition that the z resolution needs to be lower than xy, would that make sense for you?

nvladimus commented 2 years ago

Hi, yes, this makes sense, I will appreciate that. Thank you!

nvladimus commented 2 years ago

Hi, @StephanPreibisch, Sorry for bugging you, but I think the issue is still there. :pray: