Project

General

Profile

Feature #4504

Delayed fragment sends for first trigger

Added by Kurt Biery over 6 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
08/06/2013
Due date:
% Done:

0%

Estimated time:
Duration:

Description

In testing the v2e V1495 with Boris at the WH14N teststand, we noticed that when we generated individual triggers with lots of time between them that the first complete event was not received by the Aggregator until the second trigger had been generated.

We added some debugging statements to the code and found that all three fragments (one V1495 and two V1720) were being sent soon after the trigger was generated, but only the V1495 fragment was received by the first EventBuilder at that time. The fragments from the V1720s were not received until the second trigger had been generated, its fragments processed by the BoardReaders, and its fragments sent over MPI.

We should figure out what is going on here.

History

#1 Updated by Kurt Biery over 5 years ago

  • Status changed from New to Closed

This was due to an artificial delay (a sleep call) in the code that has long since been removed.



Also available in: Atom PDF