HLT1 Lumi Line

First version of Lumi Line

Resolve the Allen algorithms part of the open issue #220

Extend the hlt1_pp_default sequence with the following algorithms:

• CalcLumiSumSize

  • Read the decision of HltODINLumiLine, if the event fired the trigger, set the corresponding lumi_summary_size
    • The size is defined in device/lumi/include/LumiCounterOffsets.h

• MakeLumiSummary

  • Write the Lumi counters by a specific order into the HLTLumiSummary rawbank, with data type unsigned, and assign it to HostBuffer
    • Store multiple counters in one unsigned int
    • The order, bit offsets, and sizes are defined in the header file device/lumi/include/LumiCounterOffsets.h
  • Also with necessary ODIN information for lumi analysis
    • see discussion in twiki page DiscussionOnLumiEvents
    • event time defined as: t0 = gps - (orbit*3564 + bcid) *1000 / 40078
      • The event time is not rounded for simplicity
    • re-mapped bunch id defined as: bcid = orbit*3564 + bcid
    • bunch crossing type
  • Current counters:
    • passed GEC or not
    • the number of Velo tracks
    • the number of Velo Vertices
    • the number of SciFi clusters
    • Muon hits of region
      • M2R2
      • M2R3
      • M3R2
      • M3R3

Lumi Line uses PVs as lumi counters and requires running the Velo without GEC. This introduces a ~5% slowdown.

Update the reference files since the ordering that the MES (Multi Event Scheduler) gives is changed.

Add Rec/Allen/src/GaudiAllenLumiSummaryToRawEvent to support Moore-based Gaudi Allen configuration

• copied from Rec/Allen/src/GaudiAllenReportsToRawEvent

Merged from !765 (closed), which add lumi_summaries and lumi_summary_offsets to HostBuffer

• Also added lumi summaries to OutputHandler.
• The size of lumi summaries is expected to be much smaller than sel reports.