micro-manager icon indicating copy to clipboard operation
micro-manager copied to clipboard

uM2 gamma pixel size doesn't update with Ti2 tube lens

Open samjlord opened this issue 6 years ago • 5 comments

When I change the tube lens on the Ti2, uM2 gamma doesn't update the pixel size, unless I press the "refresh" button. In uM1.4, the pixel size changes instantaneously. When using our old Ti scope with an Arduino- and magnet-based tube lens sensor, the pixel size updates immediately in uM2 gamma. For the Ti2, the tube lens property is not included in the pixel size calibration.

(sorry, I had posted this at the older repository before: https://github.com/micro-manager/micro-manager/issues/676)

samjlord avatar Oct 21 '19 17:10 samjlord

The magnification on the TI2 seems to work ok for me.

Where are you checking what your current pixel size is? For me, I check the grid creator window in the position list, each time I open it it shows the correct size accounting for the current magnification and binning settings.

nanthony21 avatar Nov 07 '19 23:11 nanthony21

If I snap an image, change the mag to 1.5x, then snap another image, the frame size in the top of the image window does not update. I need to first close that window and snap a new image to get the correct size in microns. Also, the pixel size listed on the main uM window does not update unless I press the "refresh" button.

samjlord avatar Nov 09 '19 00:11 samjlord

I see. Have you checked the image metadata to see if the pixel size is being saved correctly? If the metadata is saving correctly and this is just a matter of the GUI labels not updating properly then I imagine this probably won't be a priority for most people.

nanthony21 avatar Nov 17 '19 20:11 nanthony21

The metadata is not saved correctly unless you first press the reset button.

samjlord avatar Nov 18 '19 17:11 samjlord

Hmm, that does seem like an issue that should be fixed. Unfortunately the solution probably lies inside the device adapter for the TI2 which is closed-source. I'm not really sure how the closed-source code is handled, is this something that Nikon needs to fix?

nanthony21 avatar Nov 20 '19 02:11 nanthony21