Closed coretl closed 9 months ago
Yes, I think the current implementation is a bug, and your proposal is correct.
I think this might potentially be useful in the context of testing, of creating particular document streams---for example, with repeated seq_num
(indicated a "rewound" plan that re-took some data points) or with missing seq_num
(not valid, but perhaps useful to construct to test failure modes).
This is handled in #272
In ComposeEvent: https://github.com/bluesky/event-model/blob/ef8ee4b6040e647883d8adbe6c5fa9da33ac984a/event_model/__init__.py#L2292-L2344
You can specify a
seq_num
, but the event counter is just incremented. Should it instead doself.event_counters[self.descriptor["name"]] = seq_num + 1
? I don't know ifseq_num
is specified anywhere, I don't think it's used in the RunEngine