The current ls_slice_settings.z_step default value is 0.313 um, equivalent to 10 mV. This mV -> um conversion came from a calibration on the argolight target, so the 0.313 um measurement is in sample space.
The lf_slice_settings.z_step default value is 0.143 um, which is the step size of the piezo in data space. The motion of the piezo corresponds to a (0.143 um)*2/1.4 = 0.205 um motion in sample space.
I'll propose that we save all scaling coordinates in sample space. I think the easiest path to this goal will be to make a change similar to #82, where we changed ls_slice_settings.z_step's units from mV to sample-space um. I'm hoping we can change lf_slice_settings.z_step's units from data-space um to sample-space um.
This issue is coupled with #85. In the short term, we're planning to modify the .zarr's scale metadata in place so that we can use clean pipelines. In the long term we're shooting to have consistent metadata coming straight off the scope.
The current
ls_slice_settings.z_stepdefault value is 0.313 um, equivalent to 10 mV. This mV -> um conversion came from a calibration on the argolight target, so the 0.313 um measurement is in sample space.The
lf_slice_settings.z_stepdefault value is 0.143 um, which is the step size of the piezo in data space. The motion of the piezo corresponds to a (0.143 um)*2/1.4 = 0.205 um motion in sample space.I'll propose that we save all scaling coordinates in sample space. I think the easiest path to this goal will be to make a change similar to #82, where we changed
ls_slice_settings.z_step's units from mV to sample-space um. I'm hoping we can changelf_slice_settings.z_step's units from data-space um to sample-space um.This issue is coupled with #85. In the short term, we're planning to modify the .zarr's scale metadata in place so that we can use clean pipelines. In the long term we're shooting to have consistent metadata coming straight off the scope.