|Elizabeth's General Working Page||A collection of database application and online information infrastructure documentation and links|
TDB Project Description |
|A description of the Run 2A Trigger Database Project and suggestions about what needs to be done for Run 2B.|
TDB Schema Description|
|A description of all Run 2A Trigger Database application tables, columns, views, roles, triggers, and other details.|
Understanding the Interfaces|
TDB Help ! ! !
|A description of the Run 2A Trigger Database Interfaces.|
|Trigger Database Interface(s)||Some Links to Trigger List information:|
|Run 2A TDB Interface Examples||
Command line |
||Run 2A (old) Trigger Meister Instructions -- 2005
Trigger Database Review
|| Trigger Database Review -- May 2005
||XML - old documentation
Trigger Database Rules Document
||a document in development intended to summarize what rules are enforced
by the Trigger Database and where those restrictions come from.
||Some example queries of the Runs, Trigger, Luminosity, SAM
Trigger - FAQs
||A collection of questions and answers about the trigger
definitions, trigger and script names, trigger operation and prescales
|| Changes needed for Global Monitor lmTrigger Application
||Instructions on running various programs (usually TMtools)
A Proposal - Sep 29, 2001
Discussion with L2
|Discussions about Trigger Configurations and Releases of L2 and L3 code.
Trigger Emulation Design Group
||Amber Boehnlein, Dan Claes, Elizabeth Gallas(chair), Philippe Laurens,
Jim Linnemann, Manuel Martin, Roger Moore, Kin Yip:
Streaming Implementation Description
||The devil is in the details.
Streaming affects Trigger, Run, Luminosity and SAM databases as well
as Level 3, COOR, and Datalogger.
Exclusive Streaming - creates book keeping nightmare.
Round Robin Streaming - a more benign choice.
I have posted my notes on how I used Steve/Matt's generic_db_server in olscvs to create the basic generated code for the trigger_db_server at dbserver_notes.txt, which is a file in a doc area in the trigger_db_server package in the d0cvs repository. These notes may be updated when I figure out how the server actually works. Rich Wellner is helping here a lot developing the methods to interface to the client code.