Trigger Database

1
Trigger Database
(D0 Collaboration Meeting. July, 2001)

• Elizabeth Gallas, Rich Wellner, Vicky White
  (Fermilab - CD)
• Regular status reports, progress can be seen on
  the Trigger Working Page at http//www-d0.fnal.g
  ov/gallas/trig/trigger.html
• Purpose of the Trigger Database
• Generate a complete set of instructions which
  specify the logical conditions which determine
  which events are recorded by the online detector
  (one of many inputs to COOR)
• Store all trigger configurations used in the
  online detector over the history of Run 2. This
  includes versioning of software and firmware
  which determine the trigger decision, which is
  not included in a real-time trigger download.

2

• Over the last 7 months
• Decisions were made, Information was collected,
  organized. Repeat n times.
• Design of the database was completed (we hope to
  the 99 level), including all levels of the
  trigger and all types of configurations.
• Extensive coding has been required for the user
  interfaces. We utilize a CORBA based database
  server to an ORACLE database.
• This database is unique because a large set of
  complex and interrelated information must be
  entered and certified by humans representing many
  sub-detectors, for the complete configuration of
  a complex device. Every collaborator
  participating in data analysis will be
  interested.
• We expect to come online in August with the
  Reporting Interfaces (showing current trigger
  lists) and specific individuals able to enter
  configurations for the online and simulated
  trigger.