Skip to content

Use the scan motor position of pixelQ when calculating geometry #3

Description

@bfrosik

With new code the Conversion (from xrayutilities) is created with the scan motor position at the max intensity.
But when calculating Astar, Bstar, Cstar the scan motor position is given as parsed from metadata, and it could be different for different beamline. Verify that each beamline uses the correct value. Also check code for calculating pixelQ and RSM for that issue.

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