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

Reconsideration of the OP_RUN request message operation #37

Open
nsoblath opened this issue May 2, 2024 · 0 comments
Open

Reconsideration of the OP_RUN request message operation #37

nsoblath opened this issue May 2, 2024 · 0 comments
Labels

Comments

@nsoblath
Copy link
Member

nsoblath commented May 2, 2024

Previously there was a 4th request message operation, OP_RUN, and I'd like to consider the possibility for putting it back in. OP_RUN was removed from the standard a while ago, but never completely removed from the codebase. You cannot currently send an OP_RUN, but some of the code for handling such messages still exists.

Psyllid has a use case where sending a "run" command would make sense. In fact, the Psyllid API still has the ability to receive OP_RUNs, plugging into the parts of dl-cpp that still exist for handling them. Psyllid has a distinct "running" state, when it's taking data.

From discussion on the Project 8 Slow Controls call (5/2/24), other opportunities for using this type of request would be mass spectrometers, and (based on the Phase II experiment) the RSA.

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

1 participant