Skip to content

Hard ware trajectories scan on p99. #26

@Relm-Arrowny

Description

@Relm-Arrowny

Goals

Acceptance criteria : What journeys should the user be able to complete to consider your feature done
Be as specific as you can, check them off once they work. Add more if you find more requirements during development. Issue should only be considered done after all of them are checked

  • Hardware triggered STXM on p99.
  • A demo showing the data corrections.

Tasks

base on the goals, deduce the tasks required. check them off once they're done

Related Resources

ophyd-async branch:
PandA for time based triggering: https://github.com/tomtrafford/ophyd-async (this was a merge of these two branches https://github.com/bluesky/ophyd-async/tree/pmac-trajectory and https://github.com/bluesky/ophyd-async/tree/scanspec-seq-trigger )

Script for the demo: https://github.com/DiamondLightSource/bluesky-sprint-demos/blob/p99-test/2024-12-01/p99.py

Metadata

Metadata

Assignees

No one assigned

    Labels

    SMGcommon to all beamlines within the groupp99

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions