|
|
|
|
|
|
|
An object-oriented compiled language, formally standardized in 1998, with an heritage from C.
Reference Link (http://www.cplusplus.com/)
A list of neutral Beta Candidates with EMC showers not matched to any charged track
Reference Link (http://www.slac.stanford.edu/BFROOT/www/Detector/Calorimeter/software/index.html)
CAMAC modules in the power supply alcove (building 624), rack 5, that trigger beam aborts if the DCH and EMC PIN diodes read values above their respective thresholds.
Reference Link (http://www.slac.stanford.edu/BFROOT/www/Detector/Backgrounds/liaisons/CBAM.html)
A data bus used by Detector Controls to obtain monitoring data, such as temperatures and voltages. See BaBar Notes 365 and 366.
List of reconstructed "candidate" particles. This term is used in the Beta analysis program package
Reference Link (http://www.slac.stanford.edu/BFROOT/www/Computing/Offline/Beta/Beta.html)
This is a manual that attempts to put in one place all the directions for how to keep the BaBar detectors, electronics, and computers running. It is stored in the BaBar CVS repositor as the project CareAndFeeding.
Reference Link (http://www.slac.stanford.edu/BFROOT/www/Detector/Operations/CareAndFeeding/care/care.html)
The "Care and Feeding of BaBar" (aka "The Care Manual") attempts to put in one place all the directions for how to keep the BaBar detectors, electronics, and computers running. It is stored in the BaBar CVS repository as the project CareAndFeeding.
Reference Link (http://www.slac.stanford.edu/BFROOT/www/Detector/Operations/CareAndFeeding/care/care.html)
CEN-BIP is an Input/Output Controller (IOC) running the VxWorks operating system and EPICS software. Its named for its main purpose which is to manage the BaBar injection. It communicates via a private network with CEN-BIC, an IOC at Main Control Center (MCC) accepting the injection after notifying the BaBar subdetectors to ramp down and getting confirmation back that all are safe. CEN-BIP denies the PEP injection if it doesn't receive the all-safe confirmation from the subdetectors. Once the injection is complete, CEN-BIP instructs the subdetectors to ramp-up to High Voltage. CEN-BIP does some other tasks as well. For eg, it keeps track of luminosity, integrating instantaneous values which are written to oracle database. It also communicates with Run Control (ORC) to inform ORC re: health of the detector and data acquistion status.
CERNLIB is a set of software libraries and programs to aid in the development of High Energy Physics applications. It includes function libraries (kernlib, mathlib, packlib etc.), histogramming facilities (HBOOK, HPLOT), the analysis tool Paw and th e simulation toolkit Geant3.
Reference Link (http://www.slac.stanford.edu/comp/physics/cernlib/cernlib.html)
A popular component of photon detectors.
A method used by EPICS applications for collecting data from monitoring VME crates. See EPICS.
B refers to B meson, charged is either electrically positive or negative, ie B+ or B-, the quark wave function of B+ is (bbar u), u is the u quark, bbar the anti b quark.
Decays of the B meson are classified according to the quark content of the final state. If there are no charm quarks c in the final state, we speak of charmless B decays. There are many examples of charmless B decays, some of them are B -> pi pi, B -> K K, B -> pi K, B -> rho rho, B -> rho K*, B -> phi K*.
Citrix is the Windows Terminal Server used at SLAC. This allows you to use windows applications from Solaris or Linux machines (or even any X-Windows terminal by running the citrix application on Solaris or Linux).
Reference Link (http://www2.slac.stanford.edu/comp/winnt/wts/citrix_at_slac.html)
A Class Library for High Energy Physics. CLHEP is part of Anaphe (ANAlysis for PHysics Experiments) which was formerly known as LHC++. Anaphe replaces CERNLIB and is written and maintained by CERN.
Reference Link (http://wwwinfo.cern.ch/asd/lhc++/clhep/)
A mult-threaded, cobra server used in Event Reconstruction to pre-create and pre-size databases and containers
Reference Link (http://www.slac.stanford.edu/BFROOT/www/Public/Computing/Databases/experts/administering.shtml)
A mult-threaded, cobra server used in Event Reconstruction to pre-create and pre-size databases and containers
Reference Link (http://www.slac.stanford.edu/BFROOT/www/Public/Computing/Databases/experts/administering.shtml)
Software that collects the error messages generated in various parts of the BaBar online system and displays them centrally.
Periodic meetings of collaborators to 1. discuss detector performance, provide a forum for short term planning of detector operations, 2. review and plan detector upgrades, 3. provide a forum to critique and improve physics analysis in preparation for conference presentations and journal articles, 4. provide an opportunity to present reports from task forces, workshops, etc.
An event collection contains references to events within the Event Store.
Reference Link (http://www.slac.stanford.edu/BFROOT/www/doc/workbook/objectivity1/objectivity1.html#collections)
Collection names are the mechanism by which collections are accessed from the BdbEventStore object.
Reference Link (http://www.slac.stanford.edu/BFROOT/www/doc/workbook/objectivity1/objectivity1.html)
Typically refering to background resulting from random combinations of charged and/or neutral particle candidates. May also refer to signal candidates which are composed of a decay in which one or more of the true daughters have been replaced by a rando m track or photon from the rest of the event.
The process of bringing a newly constructed detector into routine operation.
'Commit' is a VCS (Concurrent Version System) command that means 'commit your changes". Use this command when you wish to 'publish' your changes to other developers, by incorporating them in the source repository.
Reference Link (http://sunsite.ualberta.ca/Documentation/Gnu/cvs-1.11.1p1/html_node/cvs_6.html#SEC6)
The new BaBar computing model.
Reference Link (http://www.slac.stanford.edu/BFROOT/www/Computing/Documentation/CM2/intro/)
The committee has two functions. Firstly, steering the contributions of the Tier-A centers. Then advising the International Finance Committee on the financial value of these contributions and the size and cost of total BaBar Tier-A requirements. Secondly, advising BaBar management on computing issues affecting remote collaborators.
Reference Link (http://www.slac.stanford.edu/BFROOT/www/Computing/CSC.html)
The Conditions Database is a repository for history under which data was acquired or processed. This includes geometry, electronics calibrations, detector alignments, trigger/online/detector configuration, and recontruction adjustable parameters. The Con ditions Database is designed to allow for a complete description of the detector as a function of time, where different components of the detector may exhibit different time variances.
Reference Link (http://www.slac.stanford.edu/BFROOT/www/doc/workbook/objectivity1/objectivity1.html#condDb)
A component of the Babar on-line database, which includes the subdetector information.
Reference Link (http://www.slac.stanford.edu/BFROOT/www/Computing/Online/Databases/OnlineDatabases.html)
Data which is indexed by the configuration key. The map of crates in the partition is an example.
The structure in the control room at which the experiment is monitored and run.
Each persistent object is created in an Objectivity database and is stored in a container. One or more containers compose a database.
Reference Link (http://www.slac.stanford.edu/BFROOT/www/doc/workbook/objectivity1/objectivity1.html#terms)
Non-resonant production of primordial u u(bar), d d(bar), s s(bar) and c c(bar) quark pairs in e+e- annihilations.
The room with the console and other workstations for running the BaBar detector. The control room is located in IR2.
Standard for a serial bus used for instrumentation and control.
Reference Link (http://www.slac.stanford.edu/BFROOT/www/Computing/Online/Detector/hardware/CAN_Micro.html)
Standard for a serial bus used for instrumentation and control.
Reference Link (http://www.slac.stanford.edu/BFROOT/www/Computing/Online/Detector/hardware/CAN_Micro.html)
There are two versions of this object, BdbConversionManager and RooConversionManager, these are used to manage the input and output of data between the persistent events stores (BaBar Datastore and Kanga) and the transient job.
Tagging in BaBar is done using the Cornelius++ package. Actually, Cornelius++ is a rather general tool and can do more than just tagging. For each event, Cornelius++ can provide: the relative probability, that the tagging B was a B0 (or B0 bar), the list of particle(s) used to tag the B.
Reference Link (http://www.slac.stanford.edu/BFROOT/www/doc/workbook/analysis/analysis.html#tagging)
A commercial electronics supplier. Many BaBar high voltage power supplies are from CAEN.
Reference Link (http://www.caen.it/)
Building 621 which is attached to the IR2 hall (building 620). The first floor of the counting house houses the Control Room and the Cornelius conference room. The second floor houses the rest rooms, the kitchen, and the maintenance area.
CP transformation: combination of charge conjugation (C: particle-antiparticle exchange) and parity transformation (P: space reflection)
Reference Link (http://www.slac.stanford.edu/pubs/confproc/babar504/babar504-001.html)
Phase difference between combinations of CKM matrix elements in the so-called triangular unitarity relations. See for instance BaBar Physics Book, Section 1.4.2, p.19
Reference Link (http://www.slac.stanford.edu/cgi-wrap/getdoc/babar504-001.pdf)
Violation of the symmetry for CP transformations.
Reference Link (http://www.slac.stanford.edu/pubs/confproc/babar504/babar504-001.html)
The cross section is a representation of the quantum mechanical probability that a particular fundamental interaction will occur when a projected particle gets within an effective transverse area centered on the target particle. The cross section can be viewed as the effective area that a target presents to a projected particle.
Reference Link (http://www-ed.fnal.gov/painless/htmls/cross.html)
current is a symbolic link to the most recent release to have reached an acceptable level of quality. Acceptable is detemined by a combination of code and physics checks as defined by the QA/QC group with input from the physics groups and detector subgoups. The QA/QC coordinator determines which release this should point to.
Reference Link (http://www.slac.stanford.edu/BFROOT/www/doc/workbook/srt1/srt1.html)
Part of the EMC electronics.
Also "CX" (preferred). Historic name of a bfmail mailing list. Now refers to the BaBar computing management group.
To add an entry to the Glossary use the BaBar Glossary Submission Form.
All comments, requests, and corrections are welcome. Send them by e-mail.
Last significant update: 10-Sept-2002