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

[Bug] Saved meta info not matching to a module's measurement #43

Open
timoML opened this issue Oct 24, 2022 · 0 comments
Open

[Bug] Saved meta info not matching to a module's measurement #43

timoML opened this issue Oct 24, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@timoML
Copy link
Contributor

timoML commented Oct 24, 2022

Version

current main

What is affected by the bug?

For most measurement modules (except the new scanning toolchain), the meta-info saved from the module are the status variables at the time of hitting the save button. This doesn't necesarily correspond to the measured signal, as it is possible to change settings of the module after a measurement was finished. There are plans of the maintenance team to improve the saving behavior. Please reach out to us, if you want to participate in these efforts.

When does the bug occur?

When saving a measurement from gui or logic.

How do we replicate the issue?

Eg. for the pulsed measurement toolchain:

  1. Start a pulsed measurement
  2. Stop the measurement
  3. Change some measurement parameters, eg. the counter binwidth.
  4. Hit the save button
    => In the saved data, the meta info will contain the counter binwidth set at step (3), which is not the setting active during the measurement / defined in step (1).

Expected behavior

Meta info should be tied to a completed measurement, not the latest set settings.

Relevant log output

No response

Additional Comments

No response

Contact Details

No response

@timoML timoML added the bug Something isn't working label Oct 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant