Skip to content

Wrong Energy and Wavelength in metadata after initialize #53

Description

@michel4j

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.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions