Trigger Database Status

1
Trigger Database Status

• Elizabeth Gallas, Jeremy Simmons
• (Fermilab - Computing Division)
• See my Trigger Working Page
• http//www-d0.fnal.gov/gallas/trig/trigger.html

Calibration and Database Meeting D0 Collaboration
Meeting Oct 11, 2002
2
Trigger Database Status (1)

• Cut of server and client including John Weigands
  changes, tested, working
• Lots of changes database, server and client
  (both web and command line)
• Couple of issues
• Check of statUsed not working on update/delete
• T-Object entry on float parameters
• Anticipate server cut in next 2 weeks
• DAN changes
• Streaming changes
• Coordination with Adam and Jeremy
• To facilitate streaming development concurrent
  with other needed changes, create new struct
  adding Stream columns, duplicate methods
• Bug fix (issues above)
• A lot of new/improved documentation
• Specifically for 2 new Trigger Meisters, but also
  some general documentation in response to
  specific questions

3
Trigger Database Status (2)

• Trigger Database access
• 3 distinct roles (Jeremy, Matt)
• Any_user read-only
• Trigger Meister all buttons
• Simulator Meister
• buttons needed to make objects, neoterms, terms,
  scripts, triggers, triggerlists
• 5 people trained
• Elizabeth, Levan, Terry Wyatt, Terry Toole,Tom
  Diehl
• Trigger Database
• Now nearly 110 trigger lists
• Using command line program set_statUsed.py
• Purpose set trigger lists used online to
  permanent developed by E and John Weigand
• based on Jeremys adduser.py
• Now connected to Run Summary Db to find trigger
  lists that have been used online to set to
  permanent
• Keeping up with demand ?
• True for online, but simulation tsim_p1? list
  development lagging
• Not really a database or entry problem.

4
Trigger Database Status (3)

• Immediate demands
• Need improvements to STATUS menu
• This is where the Current Status is set but
  also how comments, Stream are changed
• Need propagation of Current status flags
• triggers/server/client Talking to Jeremy
• triggerlist transformation program
• Working now at Script Level and for L1 NT changes
• Need more sophisticated reporting interfaces to
  develop transformations of L2 and L3 filters and
  tools
• xmlGen evolution, tied to prescale generation.
• Upcoming changes L2 preprocessors, streaming.
• Also needed
• Database Support (Diana?)
• View improvements ?
• Secure Web Severs
• New Clients
• L2 preprocessors
• L1 Calorimeter programming
• Device group entry
• Allow different Devices per Exposure Group