-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
uM2 gamma pixel size doesn't update with Ti2 tube lens #78
Comments
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 |
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. |
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. |
The metadata is not saved correctly unless you first press the reset button. |
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? |
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)
The text was updated successfully, but these errors were encountered: