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

Status variables are only saved at module deactivation #223

Open
tobiasgehring opened this issue Jul 12, 2017 · 0 comments
Open

Status variables are only saved at module deactivation #223

tobiasgehring opened this issue Jul 12, 2017 · 0 comments

Comments

@tobiasgehring
Copy link
Collaborator

Status variables are saved to file at module deactivation. This means that if Windows or Qudi crashes new settings are lost.

Expected behavior (i.e. solution)

Status variables should be saved immediately.

##Other Comments
@a-stark pointed out that it is important that not all status variables are saved when only one is changed since status variables may include potentially big numpy arrays. They should only be updated when they are changed explicitly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant