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!
Simulation Home
Sim Codes
Event Generators
Bogus/BgsApp
SimApp
Bear
Moose
Fast Simulation
Geant4 Home
Subsystems
PEP
SVT
DCH
DRC
EMC
IFR
Mixing/Trigger
Backgrounds
Mixing
Trigger Simulation
MC Truth/QA
MC Truth
Micro/Mini
QA Histograms
Sim Error Reports
REMEDY
MC Production
Production Home
Test Production
Tools
Database
CERNLIB
CLHEP
Event display
RandControl
Scripts
Check this page for HTML 4.01 Transitional compliance with the
W3C Validator
(More checks...)

trgFrame status (Ed Frank) July 1996

trgFrame provides the following functions for trigger simulation studies:
  • Hit mixing between physics and multiple sources of background
  • Data and control interface between trgEM, trgDC and the reconstruction
  • Direct access to simulation data (XDR format)
  • Event and clock level synchronization of EMC and DCH trigger simulations.
  • Capability to simulate the Global Trigger
  • Simulation of the Fast Control system's clocks; conversion between clock tick, beam crossing number, and time; random synchronization of clocks
  • Random number generation interface and initialization.
Package is essentially complete. Has been used for detailed trigger simulation studies. Last tested with SRT release 1.0.3. Developed by Ed Frank (package coordinator) and Paul Dauncey.

Having built it, it is time to take it apart:

  • interface codes to the trgDC and trgEM packages
  • mixer code to the Framework
The FC clocks, global trigger, and random number components can either become packages, or migrate into the reconstruction utilities package.

Needs from other parts of simulation

  • Because of the large data samples needed to perform trigger studies, and because real analysis is done, work on trgFrame has affected the designs of the Framework, dbio (C++ -> F77 copy-back and data versioning), and the AbsEvent. On the one hand this is good, but on the other hand it distracts reconstruction design from its most immediate goals. It is important for the simulation group to realize this and therefore consider carefully any actions that lead to data versioning issues in dbio.
  • GHit dbio objects should be (1) decoupled completely from digi objects and (2) complete so that all reasonable digitization ideas can be accomplished without the need to re-simulate at the hit level.