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...)
(DhpComparisonRecord
#-------------------------------------------------------------------------
#                Comparison specifics - histogram pahts, comparisons
#                to do, etc.
#-------------------------------------------------------------------------
# Frequency for check (in seconds)
  (checkInterval  120)       

# The title of the histograms to be compared
  (title "H1d0")        

# The path to the histogram
  (path "DIR1")              

# Function to fit:
  (RefFit "Polynomial(1)+Gaussian")
# "Polynomial", "Gaussian"

# seedValues bunch the seed parameters by function component.  In
# the example below, (23,0) are the two parameters needed for a
# first order polynomial.  (50,3.08,0.010) are the area, mean and
# width of a Gaussian respectively.

  (seedValues  (23,0) (50,3.08,0.010) )        

# expectedValues bunch the expected values of the parameters by
# function component.  In the example below, ( () (0,-5,5) )
# represents the expected values for the polynomial and
# ( () (3.08,-5,5) (0.010,-5,5) ) represents the expected values
# for the Gaussian.
#
# For the polynomial, the first parameter is ignored.  The second
# parameter is expected to be 0 within +5 or -3 sigma.  If it is
# not, the confidence level will be multiplied by 0.01.  The
# confidence level is initialized to 1.
#
# For the Gaussian, the first parameter is ignored.  The second
# parameter is expected to be withing 5 sigma of 3.08 or the
# confidence level will be multiplied by 0.001.  The third
# parameter is expected to within 5 sigma of 0.010 or the
# confidence level will be multiplied by .1
  (expectedValues ( () (0,-3,5,.01) ) ( () (3.08,-5,5,.001) (0.010,-5,5,.1) ) )

# Parameters for the functions are in scientific notation, e.g.
# 314.15E-02 (or just 3.1415 will work of course)

#-------------------------------------------------------------------------
#                    Responses (can have many or only one)
#                    3 types: stream, logfile, or email
#-------------------------------------------------------------------------
 (streamResponse

# Min and Max set the confidence level range for which the result
# of a comparison will trigger this particular response.
# The values range between 0 and 1.
  (min 0)
  (max 0)

# binAlarmType is important when using a bin comparator
#  Currently, the available values are 0,1,2,3.
#   Values 0 and 1 will result in summary responses.
#    For example, in a 1D histogram if 3 channels go
#     from DEAD to HOT, then there will be a message
#     for that transition, stating that 3 channels 
#     went from DEAD to HOT.
#   Values 2 and 3 will result in individual responses.
#     For example, in a 1D histogram, if 3 channels go
#      from DEAD to HOT, then there will be 3 messages
#      for that transition, each stating the particular
#      channel number with the problem.
#   Values 0 and 2 are similar in that messages will
#     be triggered for OK to DEAD, OK to HOT, DEAD to HOT,
#     DEAD to ALIVE, HOT to DEAD, HOT TO ALIVE transitions.
#     In a logFileResponse, severities for such transitions
#     will be of level ErrLog::error, except for transitions
#     to ALIVE, where the severity will be of level ErrLog::warning.
#   Values 1 and 3 are similar in that messages will be
#     triggered for all transitions where the state changes.
#     In a logFileResponse, all severities for such
#     transitions will be of level ErrLog::error.

  (binAlarmType 0)

# the message to be streamed, should be specific enough for a person to 
# understand the system causing the failed comparison as well as the
# nature of the problem; should also be brief enough that it can be read 
# in a glance i.e. a one-liner.

  (msg "Place message here")  

# Stream Type: 1 corresponds to a screen output, 2 corresponds to a 
# file output with time-stamped entry
  (stype 1)

# File name is given by name below.  File is created
# if it doesn't exist, otherwise it is appended to.
# Name of file (see stype)
  (name "")                 

  )