-
Notifications
You must be signed in to change notification settings - Fork 24
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
Triggering of xspress3 at BMM takes 2.5s for 0.5s exposure #96
Comments
Did a few tests today with @bruceravel, all repeatable, even with the disabled HDF5 plugin. @tacaswell, what would be the best way to debug it? Which kinds of prints can help here? I guess this dispatching is doing something very slowly, but not sure how to best approach it. |
I think we may need to throw a whole lot of camonitors on the AD signals to see where it is getting stuck. If we are at the wait message, than that means we are through nslsii/nslsii/detectors/xspress3.py Lines 615 to 621 in 18c0632
|
This part of the code seems to be a bottleneck (see the attached picture with the
ts_msg_hook
-generated output):nslsii/nslsii/detectors/xspress3.py
Lines 623 to 638 in 18c0632
The text was updated successfully, but these errors were encountered: