L3Trigger (February, 1998)

Strictly speaking, there is no L3Trigger simulation. Instead, the Level 3 trigger code is being designed to allow the same code to be run in offline and OEP Frameworks.

For details on the L3 development effort, please see the Level 3 Web Page, /BFROOT/www/Detector/Trigger/Level3/ . A few issues do relate to simulation development, however, and those are listed here.

At present, Level 3 trigger code uses Digis provided by various subsystems: DCT, EMT, GLT, FCT, DCH, EMC, SVT. Converting tagged containers (TCs) to Digis will cost CPU cycles, and it is not yet clear whether L3 can afford to do it. Thus, L3 has joined OEP in requesting that all subsystems provide Digi-to-TC (as well as TC-to-Digi) conversion algorithms, in order to support performance studies. These will also be needed for all L3 simulation studies if L3 does decide to use TCs as its input format.

Level 3 will provide to reconstruction an estimate of true event time, information that the L3 algorithms glean from the event, and a record of its decisions.

Needed from others:

• Persistent-capable Digis from subsystems used by L3 trigger
• Digi-to-TC and TC-to-Digi conversion from subsystems used by L3 trigger
• L3 group is looking for help with calorimetric algorithms

Work to be done:

• Compare CPU performance using TCs vs. Digis
• Configure trigger prescaling consistent with L1GltSim and L1FctSim
• ... and much more: see L3 web page, which contains a schedule of milestones