Skip to content
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.

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

TetrAMM triggering #1023

Open
prjemian opened this issue Oct 16, 2024 · 3 comments
Open

TetrAMM triggering #1023

prjemian opened this issue Oct 16, 2024 · 3 comments
Assignees
Labels
Milestone

Comments

@prjemian
Copy link
Contributor

As a beam-position monitor, the TetrAMM should be operated in continuous mode. The trigger mode should make sure the detector ACQUIRE button is pressed and then set its status object to DONE. This will allow a subsequent .read() to return the current values.

The default .stage_sigs sets acquire to Done and the mode to Single. Change this to do none of these: .stage_sigs = {}

We found this today while running bp.rel_scan([tetramm] ...) at XPCS. The scans were getting stuck because the tetramm trigger status object never finished.

@prjemian
Copy link
Contributor Author

Watch the XPCS repo for this incoming change.

@qzhang234
Copy link

This is the scan that was stuck (first image). On second image, between scan point 15 and 16, the time gap is nearly 2 minute

image
image

@prjemian
Copy link
Contributor Author

Two commits on this:

@prjemian prjemian added this to the 1.7.2 milestone Oct 29, 2024
@prjemian prjemian added the bug label Oct 29, 2024
@prjemian prjemian self-assigned this Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants