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...)

Stripcharts for dummies

Here's the TEMPORARY official link to the OFFICIAL stripcharts!!!
To understrand how are they made and how to made them by yourself in an easy way ready the following page....

Here are the various steps needed in order to run the code that makes the stripcharts for different subdetectors-systems:

  • The code resides in OprQaUtils package
  • It has been implemented in order to be run in the following steps (if you find any error running the code please check the procedure before submitting a bug alert
  • The code is site-independant. When a new processing farm is added to the system, whoever is maintaining the code locally will need to update a list in OprQaUtils.pm
The full chain needed before runnning the tool is the following:
  • newrel -t -s $BFROOT/work/u/user 12.4.x my124x (with x>0d)
  • cd my124x
  • srtpath enter enter (this step is CRUCIAL:: every time you log of and re-log in you need to REDO srtpath)
  • addpkg workdir
  • gmake workdir.setup
  • gmake installdirs
  • addpkg OprQaUtils V00-02-02
  • gmake OprQaUtils.bin
  • cd workdir (again: step crucial:: the code is intented to be run in WORKDIR if you try other locations the paths are going to be screwed!)
  • makeStripCharts.pl

For a complete list of options you can use the command: makeStripCharts.pl -help.

REMEMBER:: all the command must be issued from the workdir

For example: I want to produce stripcharts for

  • Fully Reconstructed events ; First processing ( -fN ER7 )
  • Put the output in ~asarti/test/ER7 ( -dir ~asarti/test )
  • Run over just a given release: 12.3.4f (-rel 12.3.4f )
  • Analyize just the EMC ( -tmpsub emc )
  • Produce an html summary file named pippo.html (-index pippo.html)
  • Specify a run range: 34700-37000 ( -run 34700-37000 )

The command line should be:
makeStripcharts.pl -dir ~asarti/test -fN ER7 -rel 12.3.4f -tmpsub emc -index pippo.html -run 34700-37000

ATTENTION:: the very first time that you run the script on a customary directory it tries to write down the output specified via -dir "name" adding to the path the farm name. If the path does not exist the script makes the directory and then you can run it again and have your output were you want.

There is now the ability to choose the number of days that you wish to run strip charts for. Use the -days #number of days# option. Output will go to $BFROOT/www/Physics/BaBarData/QaOpr/Charts/{Num}days/.

For development, the make***Charts.pl scripts must be copied into the workdir, otherwise the script that will run will be the script from the RELEASE. The updated script should be compiled as usual (from the script in the package directory), and run as usual from the workdir.


ATTENTION: Whenever running "customary" queries on runs (not using the -cron option that runs over ALL the farms) you need to specify by hand the farm name via the -fN option. Otherwise the output would be garbage.


This page is maintained by Kelly Ford.
Last updated: May 2003.