New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Decide on optimal panda grid scan parameters #217

Open

olliesilvester opened this issue Aug 1, 2024 · 0 comments

Assignees

Labels

Contributor

olliesilvester commented Aug 1, 2024 •

edited

Loading

Discussions regarding PVT scans have lead to the following:

If we use time-based triggers, there will be an error in position, the size of which is somewhat determined by the run-up-distance.
If we use position-based triggers, there will be an error in time. To account for this, we would need to use the Eiger's variable exposure time and analysis would need to correctly weigh the positions based on their exposure time

We are trying 1. for now.

Lower run-up distance means faster grid scan but more inaccurate trigger positions. We need to work out the lowest acceptable run-up distance.

Acceptance Criteria

Use panda grid scans for a few days with PCAP enabled, varying the run-up distance and measuring total time taken
Analyse the PCAP h5 files to see exactly how run-up affects trigger position accuracy and total time, and ultimately decide on the best number to use.

Requires DiamondLightSource/hyperion#1474 and DiamondLightSource/hyperion#1485

olliesilvester changed the title ~~Decide on optimal panda grid scan speed~~ Decide on optimal panda grid scan parameters

DominicOram assigned olliesilvester

DominicOram added the hyperion label

DominicOram transferred this issue from DiamondLightSource/hyperion

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment