Skip to content

gridscan processing should determine the y- and z- coordinate axes from ISPyB data rather than using the ID #322

Description

@rtuck99

Whilst testing release 1.5.7 of Hyperion, which has changes that adjust the ordering of the xy and xz Data Collections such that either one may be the first DataCollection (as sorted by Data Collection ID) it was found that the zocalo results from grid scan processing came back with the y- and z- coordinates of the centres swapped.

When processing the gridscan data, dlstbx should be using the omegaStart values to determine which gridscan plane comes from which DataCollection.

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