The Trigger Database Status WRT Streaming

1
The Trigger DatabaseStatus WRT Streaming

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

Tools Group Meeting D0 Workshop at Oklahoma July
11, 2002
2
Trigger Database Status

• Keeping up with demand
• (http//www-d0.fnal.gov/gallas/trig/trigger.html)
  
• Immediate demands
• always new triggerlists (90 now in database)
• database server evolution/bugs/cleanup
• statUsed settings (triggers/server/client)
• triggerlist transformation program
• imposing rules on triggerlists, names
• Client fixes
• neoterms, objects, terms, scripts, tnames,tlists
• maintain
• command line packages (rcpGen )
• xmlGen evolution
• clientDemo cleanup
• New Client
• L2 preprocessors
• L1 Calorimeter programming
• Allow different Devices per Exposure Group

3
Trigger Database - Streaming

• Adam/Jeremy
• Developing streaming tools using already existing
  stream info in TDB (default primal_streams of
  filters or assigned streams to filter instances)
• Elizabeth/Jeremy TDB Changes
• Add columns to TDB tables
• Trigger List table
• Accommodate trigger lists to date (OneStream)
• Trigger Name table
• Accommodate special triggers (exclusive)
• Need to coordinate corresponding
• TDB server changes and
• TDB client changes
• Need designated STREAM NAME TABLES
• All applications share (TDB, RunS, SAM, L3 )
• Each application now has its own list (causing
  problems)
• Need two tables (offline database), separate
  application?
• Primal Streams
• Physical Streams
• Need to decide how these streams are
• Determined (authorized)