Status of the Trigger Database

1
Status of the Trigger Database

• Elizabeth Gallas, Rich Wellner, Ruth Pordes,
• Jeremy Simmons, Matt Vranicar, Vicky White
• (Fermilab - Computing Division)
• See my Trigger Working Page
• http//www-d0.fnal.gov/gallas/trig/trigger.html

Database meeting Nov 19, 2001
2
Progress, Status

• GOAL have online global trigger lists in the
  database when Run 2 resumes
• cosmic ray data taking, global collider data
  taking.
• CLIENT many changes
• new L1 functionality. Can now enter NEOTERMs
• need new cut (coordinate w/cut of server)
• SERVER many changes
• InTrigger.py, TriggerImpl.py many changes
• need to fix a case problem, make the cut
• help from Jeremy ! (cant do halfway)
• After cut, for simulation and online trigger
  lists
• Entering new L1 Muon NEOTERM, plus some Cal
• make new trigger lists
• L1 Dialogs
• not done (need for phase 1)
• proposal tying TL to L2, L3 Releases (schema
  change)
• Ruth will help
• DATABASE
• Entering backlog of changes.
• finding/removing junk records from database
  (affect status changes)

3
TO DO Summary

• Phase 1 (both in progress)
• J/E L1 reference set (L1 Dialog)
• E Neoterms
• Phase 2 (client)
• Implement User dependent actions
• give different roles different buttons
• allow users to update, delete their own
  elements
• L2 Preprocessor
• association with L2 global terms
• Devices, Device Groups for Exposure and TL
• Streams
• tie to Releases
• Phase 3 (client)
• NTY Simulations
• Prescales
• Phase 4 (since design is incomplete)
• L1 Simulation to Firmware
• L1 board registry (no server methods exist)

4
TO DO Summary

• Client Web Entry Interface
• Phase 1
• Current Status Entry
• L1 reference set (L1 Dialog)
• Neoterms
• Phase 2
• Implement User dependent actions
• L2 Preprocessor
• association with L2 global terms
• Devices
• Device Groups for EGroups
• Devices directly in a config
• Prescales
• Streams
• Phase 3
• L1 Simulation to Firmware
• L1 board registry

• TriggerDbServer
• 11 method sets tested
• get,
• insert,
• update,
• delete
• safe update
• 12 new method sets need to be tested (exist) but
  the following methods are not in clientDemo
• GetNeoTerms,
• SafeUTLPrescales,
• All NTYSimulations,
• All L2PreProcessor methods Get, Update, Delete,
  SafeU
• One set of methods remaining
• L1 board registry