You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is an existing EventHeader class that holds a subset of the information from the Heartbeat packer. I PR #33 I have extended it to add a subset of the information from the proposed CFO EventWindow Data Record.
This presumes that the CFO EventWindow Data Record is available in the trigger processes. I have not yet seen the plan for that and would appreciate seeing it ( I understand that it may already exist).
My intention for the EventHeader class is to include the subset of information that will be useful to code running in the art based trigger processes and in the offline environment. This ignores some information that might be useful for debugging.
We should discuss if we need other classes to represent the full information from these two packets in a way thats convenient for downstream offline code. The information will be available in the raw data. So question is if we want to dig it out and package all of it for use in downstream code. If so, do we want to extend the Headerclass to include all of it or do we want to provide a second class that includes the missing parts and would normally be dropped from the standard output files.
The text was updated successfully, but these errors were encountered:
There is an existing EventHeader class that holds a subset of the information from the Heartbeat packer. I PR #33 I have extended it to add a subset of the information from the proposed CFO EventWindow Data Record.
This presumes that the CFO EventWindow Data Record is available in the trigger processes. I have not yet seen the plan for that and would appreciate seeing it ( I understand that it may already exist).
My intention for the EventHeader class is to include the subset of information that will be useful to code running in the art based trigger processes and in the offline environment. This ignores some information that might be useful for debugging.
We should discuss if we need other classes to represent the full information from these two packets in a way thats convenient for downstream offline code. The information will be available in the raw data. So question is if we want to dig it out and package all of it for use in downstream code. If so, do we want to extend the Headerclass to include all of it or do we want to provide a second class that includes the missing parts and would normally be dropped from the standard output files.
The text was updated successfully, but these errors were encountered: