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
Add an 'event' command #941
Comments
Having just written that, I have just thought of one such situation where we need |
Will a description document be generated that relates to this event document? Will there be a 1-to-1 relationship for such description documents when an event is generated this way? |
Yes, the behavior of the RunEngine would be precisely identical in these two modes. It simplify removes the overhead of processing multiple Msgs. |
I think I understand. Consider this scenario:
generates two descriptor documents, essentially duplicates but for UUID. If so, can some smarts be added in RE to see if a descriptor has already been generated for the same signal list: |
Yes, in fact those smarts already exist:
I would apply the same logic to
|
Suggestion by @tacaswell which I am just recording:
Add an
'event'
command so thatcan be accomplished by
There is really no reason one should need to interleave other commands between these;
there is no situation we can think of where[edit: see next comment] This is a nice simplification.'event'
is not sufficient.The text was updated successfully, but these errors were encountered: