# Presentation: 715655

## The D0 Trigger Database Application

**Elizabeth Gallas**
- FNAL CD / Run 2 D0  C&A
**Margherita Vittone,Steve White,Eric Wicklund**
- FNAL CD / CEPA / Database Software (L.Lueking)

**Annual D0 Database Taking Stock Meeting**
**June 6, 2005 10 am FCC1**

- D0 Trigger Database

- Elizabeth Gallas              June 6, 2005

## Trigger Database Application Components

- D0 offline production database instance (d0ofprd1)
- About 40 Tables in Oracle
- About 25 Views in Oracle
- Documentation
- Web based html
- TDB Report Interface.
_**Web based interfaces:**_
_**TDB Entry Interface                   (about 13 modules)  ****_
_**TDB Report Interface                 (about 14 modules)**_
- TDB MISWEB Interface
_**Trigger Db Server**_
_**Like the SAM db servers –           **_
_**a customized db server**_

- Command line interfaces:
- DeleteTemporaryElements.py**
- CheckStatCurr.py		  **
- CheckStatUsed.py 	 	  **
- clientDemo.py  		  **
- add_user.py
- rcpGen.py  	 	  **
- set_statUsed.py
_**xmlgen.py **_
- GetBitNames.py
- GetRuns.py
- GetStuff3.py
- l3tooltype.py
- streamXmlGen.py
- ** - interfaces using the TriggerDbServer

- D0 Trigger Database

- Elizabeth Gallas              June 6, 2005

## Project Deliverables Status

- IN USE since December 2001
- all Global (Physics) and nearly all Special Runs
- a number of Commissioning and Calibration configurations as functionality of trigger systems come online
- Now contains nearly 100,000 records
- 376 Trigger Lists (nearly 5000 Triggers defined)
- single List can contain 1000s of parameters
- >250 Trigger Lists used online in >20000 Physics Runs
- All data is entered by people (10 certified)
- Trigger Lists are a unique combination of conditions which are designed individually to configure a complex system
- Nearly no duplicate records
- Once a trigger list element is created, other trigger lists can use it
- not large by database standards
- but implementation is complex, reflective of programmability of the D0 Trigger System

- D0 Trigger Database

- Elizabeth Gallas              June 6, 2005

## D0 TDB Application Project Status

**From 2001 to summer 2004:**
**Critical to the online operation of D0**
**Gradual improvement in the system since 2001 until summer 2004**
**D0 Trigger Steering Committee recognized **
**The system meets some but not all of the  requirements for its current capabilities**
**The system needs to be expanded**
**Since Fall 2004**
**Accelerated improvements in the system with help from Lee’s group (Margherita , Steve and Eric)**
**May 18, 2005**
**Trigger Database Review by D0 Trigger System Experts**

- D0 Trigger Database

- Elizabeth Gallas              June 6, 2005

## TDB Review

**May 18, 2005 1-6pm Racetrack**
**Review web page summary:**
**www-d0.fnal.gov/~gallas/d0_private/trig/ TDB_Review_0505.html**
**D0 Trigger Database Project Plan:**
**http://d0db-dev.fnal.gov:8514/atrig/TDB_Plan.html**
**last edited September 2004**
**new version after production cut**
**Report of the Committee is not completed yet...**

- D0 Trigger Database

- Elizabeth Gallas              June 6, 2005

## Effort Profile (Past and Current)

- People who have worked on this project (FNAL CD):
- Elizabeth Gallas, Vicky White, Jeremy Simmons, Matt Vranicar, Rich Wellner, John Weigand, Vijay Murthi, Steve White, Adam Lyon.
- People currently working on the project (FNAL CD):
- Elizabeth Gallas
- Margherita Vittone – web Entry Interface (client using db server)
- Steve White – trigger db server and client interface to server
- Eric Wickland – web Report Interface (client using dcoracle)
- List of tasks (next  3 slides)

- D0 Trigger Database

- Elizabeth Gallas              June 6, 2005

## List of Tasks (1): Tasks to fix/implement Entry/Report client and DbServer

**Project Plan – A lot of progress **
**TriggerDbServer - convert from fnorb to omniorb, clean up**
**Steve While**
**Entry Client: trigdb_status, l1dialogs, neoterms**
**Margherita Vittone**
**Report Client: tdb_objects, terms, L1dialogs, neoterms**
**Eric Wicklund**
**Project Plan – Next items in the schedule**
**tdb_scripts, tn, tl, tldependency**
**trigdb_objects, terms, scripts, triggernames, triggerlists**
**trigdb_tltransformation (expert required)**
**t(rig)db_L2pp, t(rig)db_ed, dg**

- D0 Trigger Database

- Elizabeth Gallas              June 6, 2005

## List of Tasks (2): Tasks for Maintenance, Integrity and New Functions

**As needed items:**
**Enforcing system constraints**
**more checks insure correct configuration**
**Performance Issues**
**needed**
**Machine Issues**
**on order for Luminosity Database**
**Clean up program**
**2-4 weeks (implementation dependent)**
**Changes to Level 1 Exposure Group Rules**
**2-4 weeks**
**Level 1 Pseudoterm Implementation**
**2-4 months**
**Trigger List to Release correspondence**
**4 weeks**
**Run 2b Changes**
**specification dependent (Vancouver)**
**Level 1 subdetector version tracking**
**specification dependent**
**Additional COOR functionality**
**specification dependent**

- D0 Trigger Database

- Elizabeth Gallas              June 6, 2005

## List of Tasks (3): Some Requests since September 2004

**L1 Calorimeter Region and Quadrant Terms**
**Level 2 trigger configuration**
**Splitting**
**ORing**
**Calorimeter Calibration**
**New tools and filters at Level 2 and Level 3**
**L3 **
**ScriptRunner Directives **
**Beam spot and magnet polarity**
**Round Robin Streaming**

- D0 Trigger Database

- Elizabeth Gallas              June 6, 2005

## Risks, Problems and Related Issues

- For Trigger DB:  Requests for changes are constant
- many requests are valid and worth pursuing (physics)
- many have been implemented
- requires thoughtful analysis and specification of requests
- assess extent of changes to existing TrigDB implementation and how it fits into the existing schedule, backward compatibility
- assess extent of changes to other online systems, communication
- many requests not mitigated by D0 management, TB (incoherent)
- source of constant distraction
- some guidelines for limiting the system should be in place
- must understand the cost of implementation on all affected systems
- Note: managing hundreds (thousands?) of triggers is not trivial
- Not just for Trigger DB, but Online and Luminosity as well.

- D0 Trigger Database

- Elizabeth Gallas              June 6, 2005

## Notes in Summary

- Trigger DB is
- a complex application
- a working application
- Note: At no point has anyone worked on this application full time and at times no one has been working on it
- manpower shortfall caused us to fall behind the needs of the experiment
- We are catching up thanks to help (CD CEPA Group)
- Margherita, Steve and Eric – CEPA group (Lee Lueking)
- kick start:  have contributed hundreds of lines of code
- satisfying specified goals of the project plan
- Catching up also helps in case of failure
- more people knowledgeable about application
- Moving forward in Trigger Project Plan
- some of the next tasks are more complex (before new features)
- Review Committee Report not expected to change the near term plan...

- D0 Trigger Database

- Elizabeth Gallas              June 6, 2005