D0 Luminosity Database Application

The purpose of this web page is to document the components of the Luminosity Database Application for Luminosity experts.
The sections below outline the application components. Details should reside in the package componente documentation in cvs, not here.
Table of Contents (links to sections below):

Purpose/Requirements - Luminosity Database Application

The Luminosity Database Application is a component of the D0 Luminosity System organized by the
D0 Luminosity Group.
This database-based effort started in earnest in December 2003 and has made considerable progress, using part of what had been developed previously by departing members of the group.

The Luminosity Database Application is a large scale and complex project which, at it's core, relies upon a set of 37 database tables and 2 views stored in the D0 offline Oracle Database production instance (d0ofprd1) with a development version stored in the development instance (d0ofdev1).

The tables constitute an offline repository for information from many subsystems:
SubsystemType/Use of information
Luminosity Monitor Detector both fundamental and derived information needed for normalization calculation and cross checks
Trigger Framework needed for normalization calculation and cross checks
Level 3 needed for normalization calculation and cross checks
Fermilab Tevatron Accelerator needed for normalization calculation and cross checks
Offline Data Processing (SAM) used to verify and certify data integrity through offline reconstruction processing and re-processing
"Group" assigned quality quality flags assigned offline by detector groups on the quality of their subsystem for that LBN
"Consistency" determined quality cross checks on internal luminosity detector information with that from systems outside the luminosity detector

The Luminosity Database facilitates the following essential operations for the D0 experiment:

End of Purpose/Requirements section.
The sections below describe the components of the system.

The Luminosity Database in Oracle

Elizabeth Gallas, Margherita Vittone.

Central to the Offline Luminosity Database Application is a set of 37 database tables and 2 database views in the D0 offline software environment. The database tables were laid out using the Oracle Designer tool, which generated the ddl (database definition language) files which create the database entities (tables, views, indexes, keys...)

A description of the database, it's tables, and all of the columns in every table is described in the following document:

Luminosity Database Document: Design, Tables, Columns ... .

Loading Online Information

Loading Offline Information

Getting information out of the database


Luminosity information is provided only for triggers and lm_access package allows to find out three types of luminosity: triggered, recorded, and reconstructed. For an explanation of these terms look at DØ notes 3971, 3972. In case of triggered and recorded luminosity no checks are performed on release information. Triggered luminosity corresponds to the trigger luminosity at L1 level while recorded luminosity takes into account the event losses in DØ DAQ system and hence it corresponds to the luminosity in raw files. CVS packages: User documentation: Expert documentation:

Data Quality

When the Luminosity Database Application goes into full production mode, LBN based data quality assessments will become possible (in addition to Run based data quality).

CVS package:

User documentation: Expert documentation:
Luminosity Group:
LumID Home
Offline Software:
LumDBApp Home
Operations Reports:
Query Menu
Back to TOP
of this document

Jim Linnemann
Last modified: Wed Sep 2 13:33:19 CDT 2009