DiamondLightSource / DiamondLightSource/mx-bluesky
Discuss and rationalise the `read_hardware` plans
Open
- Dominant language
- Python
- Stars
- 4
- Forks
- 5
- Avg merge
- 1d 30m
- Merged PRs (30d)
- 2
Description
Inside `read_hardware_for_setup` we now have many `read_hardware_xxx` plans, which are now getting a bit unwieldy. We should have a discussion about how we want these to be organised and implement the proposed solution (maybe as a new issue if complex).
## Acceptance Criteria
* Meeting had to discuss the structure of the `read_hardware_xx`
* Decisions on optimal structure are written up
* Structure is implemented (or new issues created for doing so)
Contributor guide
Assessment
This issue has not been assessed yet.