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

Wrong Energy and Wavelength in metadata after initialize #53

Open
michel4j opened this issue Jan 4, 2022 · 0 comments
Open

Wrong Energy and Wavelength in metadata after initialize #53

michel4j opened this issue Jan 4, 2022 · 0 comments

Comments

@michel4j
Copy link

michel4j commented Jan 4, 2022

If you initialize the detector and try to acquire data at an energy that is the same as the value currently set values in AD, the new values are not sent to the detector resulting in the wrong metadata.

I believe this is caused by the WavelengthEps_RBV and EnergyEps_RBV preventing AD from sending energy values that are close to the previous values. But after initialization, the internal energy value within the controller is set to 8047.78 which differs from what AD thinks it is.

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

No branches or pull requests

1 participant