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!
Comp. Search
Who's who?
Meetings
FAQ Homepage
Archive
Environment
Administration
New User Info.
Web Info/Tools
Monitoring
Training
Tools & Utils
Programming
C++ Standard
SRT, AFS, CVS
QA and QC
Remedy
Histogramming
Operations
PromptReco
Simulation Production
Online SW
Dataflow
Detector Control
Evt Processing
Run Control
Calibration
Databases
Offline
Workbook
Coding Standards
Simulation
Reconstruction
Prompt Reco.
BaBar Grid
Data Distribution
Beta & BetaTools
Kanga & Root
Analysis Tools
RooFit Toolkit
Data Management
Data Quality
Event display
Event Browser
Code releases
Databases
Check this page for HTML 4.01 Transitional compliance with the
W3C Validator
(More checks...)

Plots of the configuration and alias trees

Here you can find the plots of the configuration trees. The plots are created every day around midnight, if you need to see newer data (changed today) contact the page maintainer. Because our configuration trees are big and involved it is impossible to fit everything on one page, so the whole configration tree was split into the number of subtrees: system runtypes and system configurations.

Every object on the plots contains some information about it. First all objects are shown inside their respective containers, containers are shown as blue boxes with the container name above it (format is "sys/container"). The objects themselves are shown as boxes or ovals. Boxes are the ordinary configuration objects (leafs of the tree), and ovals are the maps. Inside box or oval there is a list of the object's names and its key. All the lines but last one show the object names, these have format /sys/RUNTYPE/path or .../name. In the first case it is understood that the object can be reached from the "sys"'s alias map and run type "RUNTYPE" and going all the way down the rest of the path. In the second case it is understood that the object is referenced under the name "name" from all its parents (or at least those present on the graph). The bottom line contains the object's key in case of the numeric objects or alias name in case of alias trees.

[Until the adoption of the alias trees their plots are generated from my personal federation -- Andy]

System runtypes

There is a separate plot for each subsystem which defines run types (there are no TOP run types in the alias trees). Each plot contains two-layer graph. The upper (leftmost) layer containing top maps corresponding to the subsystem aliases. Lower (rightmost) layer shows the subsystems' maps referenced by the top maps.

  Numeric tree Alias tree
DCH [PDF] [PDF]
DRC [PDF] [PDF]
EMC [PDF] [PDF]
EMT [PDF] [PDF]
IFR [PDF] [PDF]
ORC [PDF] [PDF]
SVT [PDF] [PDF]
TOP [PDF]  

System configurations

These plots show all subsystem objects referenced from any runtype including other subsystems' runtypes (that is all configurations currently in use)
  Numeric tree Alias tree
DCH [PDF] [PDF]
DCT [PDF] [PDF]
DRC [PDF] [PDF]
EMC [PDF] [PDF]
EMT [PDF] [PDF]
GLT [PDF] [PDF]
IFR [PDF] [PDF]
L3D [PDF] [PDF]
ORC [PDF] [PDF]
SVT [PDF] [PDF]
TRG [PDF] [PDF]

Some other plots

  Numeric tree Alias tree
ORC PHYSICS & COSMICS [PDF] [PDF]

Page Maintainer(s): Andy Salnikov,
Page Creator(s): Andy Salnikov,
Last significant update: Apr-03-2002 Expiry date: Every midnight