Skip to content

Pu00 pulse metadata#3

Open
Tom-Willemsen wants to merge 7 commits intomasterfrom
pu00_pulse_metadata
Open

Pu00 pulse metadata#3
Tom-Willemsen wants to merge 7 commits intomasterfrom
pu00_pulse_metadata

Conversation

@Tom-Willemsen
Copy link
Member

@Tom-Willemsen Tom-Willemsen commented Mar 4, 2026

Description of Work

Proposal for pu00 pulse metadata schema.

As discussed with data-streaming group Feburary 2026; this schema would be emitted:

  • once per frame by VXI control board (where vetos would just be global vetos)
  • once per frame by kafka_event_aggregator (where vetos would then be ORed with vetos from individual detectors)

Questions:

  • Is there anything missing here?
  • This is catering for two slightly different but tightly related use-cases; is it right to use the same schema for both?
  • Do the vetos from individual detectors also come in using this schema?
    • If so does this schema need some notion of "which detector module did I come from"?

In case anyone finds it more obvious, this is how this schema is intended to be used in the rawEvents and events streams:

image

@rerpha
Copy link

rerpha commented Mar 4, 2026

does this cover the "soft-vetoed" case?

@Tom-Willemsen
Copy link
Member Author

I think that:

  • If soft-veto, veto flags will be non-zero but will still get corresponding events
  • If hard-veto, veto flags will be non-zero and will not get corresponding event

So I think this schema covers both.

There is an assumption that all veto flags fit in a u32 which we should check with DSG.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants