Skip to content
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

Need to be able to store AO setup for logging and reuse. #13

Open
iandobbie opened this issue Nov 6, 2018 · 3 comments
Open

Need to be able to store AO setup for logging and reuse. #13

iandobbie opened this issue Nov 6, 2018 · 3 comments

Comments

@iandobbie
Copy link
Member

We need some functions and a file definition to allow dump and restore of AO settings.

@iandobbie
Copy link
Member Author

I believe that Nicks code now stores AO settings, not sure how easy it is to load them.

@NickHallPhysics
Copy link
Collaborator

At this point, I only store the aberrations applied once a sensorless correction has been performed. It's stored in a log file in the LocalAppData called 'sensorless_AO_logger.txt'. Lines 876-885 of the cockpit/device/microscopeDeformableMirror.py deals with this. It stores the time stamp, the aberrations measured (and therefore corrected for) and the actuator positions applied.

Currently, we don't store the actuator positions at any other time, but you can retrieve the last actuator positions applied by calling get_last_actuator_values() from the Pyro remote.

The ROI coordinates, control matrix and system flat values are stored in the config.py file in LocalAppData.

@iandobbie
Copy link
Member Author

These data are stored, but I think at least the control matrix and possibly the system flat should be stored in the global rather than local config files. We have been bitten badly in the last week with not realising the control matrix is user specific and must be reloaded or regenerated for each user.

@carandraug carandraug transferred this issue from microscope-cockpit/cockpit May 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants