Bug in the CFO/DTC operation - the first heartbeats sent do not follow the event tag number set in the runplan

Mu2e / otsdaq_mu2e

Mu2e customizations for otsdaq

Other

1 stars 5 forks source link

Bug in the CFO/DTC operation - the first heartbeats sent do not follow the event tag number set in the runplan #40

Closed grakness closed 2 months ago

grakness commented 10 months ago

Upon launching a new plan the first few heartbeats sent (9 to be exact) do not have the event tag numbers that was set initially in the runplan. After these 9 heartbeats the following heartbeat has the event window tag number that was set in the runplan. These first 9 heartbeats look like remnants from the previous run. In the attachments there's a vivado_lab screenshot and the CFOCommands.txt file (which defines the runplan).

Screenshot_20231110_180201

Screenshot_20231110_180005

rrivera747 commented 9 months ago

This bug should be addressed by new CFO version CFO2023Nov09_11_22.1

Will close after confirmation from STM team.

rrivera747 commented 2 months ago

Bug confirmed fixed. As of today, CFO version has no open issues: CFO2024Jun21_15_22.1