DiamondLightSource / DiamondLightSource/mx-bluesky
Use an accurate run time when checking for topup
Open
enhancement
hyperion
- Dominant language
- Python
- Stars
- 4
- Forks
- 5
- Avg merge
- 1d 30m
- Merged PRs (30d)
- 2
Description
The top up plan uses a constant in seconds to account for rotation, time for x-ray centering etc. This is added to the total exposure time of the collection
At the moment this constant is hard coded to a random number and passed as an argument to the `check_topuup_and_wait_if_necessary` function (with a default set to 30 s).
We should figure out an accurate value for this additional time depending on what kind of collection is being run.
Contributor guide
Assessment
This issue has not been assessed yet.