Status of the Trigger Database

1
Status of the Trigger Database

• Elizabeth Gallas, Rich Wellner, Vicky White
• Fermilab - Computing Division

D0 Collaboration Meeting February 7, 2001
2
Trigger Database - current status

• The Trigger Database currently built on the
  offline development platform includes all (3)
  levels of the trigger
• contains all L3 tool and filter definitions from
  the L3 database
• contains trigger lists for
• current online running
• trigger simulation
• early physics running
• This data was loaded using a backdoor method to
  test functionality and operations scripts like
• python interface to COOR including
• writing filter and tool parameter value
  requirements for L3 SCRIPTRUNNER
• Thanks to Computing Division for manpower !!
• Rich Wellner is contributing database server
  expertise and helping to code user interfaces for
  trigger list entry/report for data-taking and
  simulation
• Trigger db server functionality is growing daily

3
Trigger Database - current activities

• Working on user interfaces (using)
• trigger database server
• python CGI programs
• Highest level trigger list formation must be more
  sophisticated -- JSP interface
• Issues to be resolved
• streaming
• exposure groups, readout sectors for L1
• Database security (tricky issue)
• transfer of lists online/offline
• allow trigger lists for trigger simulation users
• prevent unauthorized trigger configurations from
  being used online
• prevent modification of trigger configurations
  used to record real data
• Anyone wanting to enter trigger information for
  simulation or online must get a database account.
  If you feel you need special privileges, contact
  me.

4
Still on my checklist

• L1 Calorimeter versioning (Philippe)
• (other L1 subsystems have Trigger Managers
  and how these L1 systems evolve is resolved in
  principle)
• Enter specified TM terms
• Thanks Ken (Muon) and Kin (CTT)
• Need TM terms for FPS, FPD, LUM
• (LUM using Run 1 electronics now)
• accommodate non-L1-detector L1 terms (Dan
  Edmunds)
• use of L1 cal quadrant and region terms outside
  of pseudo-terms (Philippe)
• L1 pseudo-terms and their versioning (Steve Gross
  - MSU)
• interface to hardware and luminosity databases
  (online)
• versioning at the L2 object and preprocessor
  levels, any online checking?

5
Making of a Trigger List

• Insert Trigger Objects and their parameters
• L1, L2, L3 filter and tool objects
• Insert Trigger Terms and their parameter values
• L1 and/or terms, L2 globals, L3 filters
• Terms are combined into TriggerScripts at
  each trigger level
• A Trigger unique combination of a L1,L2andL3
  TriggerScript
• A Trigger is identified by a Trigger Name which
  is lt16 chars to be stored on the thumbnail
• Form a Trigger List from one or more Triggers
• Enter TM terms and L1 Calorimeter refsets passed
  by COOR
• Enter L2 object dialog passed by COOR
• Versioning
• Increment L1 NEOTERM versions
• interface to guide hardware expert through a
  series of inserts into NEOTYPE, NEOTERM,
  NT_CHANGE, L1_BOARD, and L1B_COMPONENTS tables
• create new trigger list based on those NEOTERMS
• Increment L2 object or L3 filter or tool object
  versions
• Insert L3 Stream and/or rate information
• Enter prescale sets for a specific trigger list
• check validity of trigger list for use online
• display trigger lists