L0 Event Model

The L0 Event Model is made of four components, as is the hardware.

  • L0Calo : Inputs are extracted from the Raw Buffer, and are the 8 bit transverse energy (ECAL, HCAL) and the trigger bits for PRS and SPD. These are described in L0CaloAdc and L0PrsSpdHit. The result of the processing is L0CaloCandidate which is available in two containers, one with all non-zero candidates, and one with the highest candidate of each type. The first one is what will be put in the Raw Buffer, the second one is the input to L0 Decision Unit.

The L0Muon stores in raw banks :

* The input data received from the muon detector * All candidates that were found by the L0Muon processor * The selected candidates (up to 2 per quarter) that were sent to the L0DU to build up the L0 decision. * Eventually errors that were detected by the hardware during the processing.

The decoding of these banks or the L0Muon emulator fill containers that are stored in the TES:

  • PileUpSystem

  • L0DU : Inputs are from the three other systems. An EDMS document is in preparation to specify the exact bit assignment, see EDMS 528259. The output is basically the decision, in L0DUReport. The PUS information is added in the L1 Buffer, and it is foreseen to add information in the Raw Buffer, but this is not currently done. A tentative desciption is available in LHCb Note 2003-065.

-- OlivierCallot - 26 Jul 2005

Edit | Attach | Watch | Print version | History: r8 | r6 < r5 < r4 < r3 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r4 - 2008-10-01 - JulienCogan
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LHCb All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback