SLAC PEP-II
BABAR
SLAC<->RAL
Babar logo
HEPIC E,S & H Databases PDG HEP preprints
Organization Detector Computing Physics Documentation
Personnel Glossary Sitemap Search Hypernews
Unwrap page!
Det. Search
Who's who?
Meetings
FAQ
Images
Archive
Systems
Performance
Intern. region
Vertex Tracker
Drift chamber
DIRC
Calorimeter
IFR
LST
Magnet
Electronics
Trigger
Operations
Run Coordination
Contact Experts
Shift Takers Info
Operations Manual
Electronic Logbook
Ops Hypernews
Shift Signup
Check this page for HTML 4.01 Transitional compliance with the
W3C Validator
(More checks...)

Instructions for L3TriggerDb

Jim Panetta, Last update: 10 April, 2002

The application L3TriggerDbApp is mainly useful for running the L3 algorithms against an Objectivity database. One beneficial side affect to this application is that one can also view these events with the Level 3 event display.

L3TriggerDbApp is built on a semi-regular schedule by the L3 group. These builds are placed in the directory /nfs/bbr-nfs03/detector/trg with names that follow the convention <release>.L3Db. At the time of writing, this release is 11.8.0.L3Db.

Running L3TriggerDbApp is straightforward.

  1. Set the environment variable OEPCONFIGKEY to the configuration key needed.
  2. Set OO_FD_BOOT to point to a useful database.
  3. From the workdir directory, run the application with a tcl file that looks like the example file ExampleL3Db.tcl. This file is reproduced below.

The workdir permissions are set to drwxrwsr-x so that users may use their own custom tcl files.

By default, the L3 event display module is disabled. If the L3 event display is required, simply set the environment variable L3DISPLAY to true and run L3TriggerDbApp as above. The display will open on the first event automatically.

Common Problems

  • Problem: Mysterious complaints from BdbWhatever and a core dump.
    Solution: This version of L3TriggerDbApp was built against a release other than the release used to fill the database schema. Try a different version of L3TriggerDbApp or a different database.
  • Problem: L3 is using a really weird configuration.
    Solution: You need to set the environment variable OEPCONFIGKEY. Otherwise you get the very old config alias SP2.

ExampleL3Db.tcl

mod talk BdbEventInput
  input add /users/panetta/SimApp/mu_pair_900500_1k_aug01
  input add /users/panetta/SimApp/mu_pair_900501_1k_aug01
exit

sourceFoundFile L3TriggerDb/L3TriggerDbApp.tcl

Jim Panetta
Last modified: Wed Apr 10 20:45:54 PDT 2002