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

Program Timing -- CpuCheck module


  • Include the CpuCheck module in your program. Here is an example from $BFDIST/releases/7.12.5/BbsimModule/AppUserBuild.cc.
    #include "RecoUtils/CpuCheck.hh"
    add (new CpuCheck( "CpuCheck", "Check if there is remaining CPU time."));
    
  • Make sure the module is in your tcl path, and is active. This is what you need if your program uses AllPath.
    path append AllPath CpuCheck
    mod enable CpuCheck
    
  • Set the print frequency, e.g.
    mod talk CpuCheck
    CpuCheck> printPeriod set 1
    CpuCheck> exit
    
  • Run the program. Looks for lines like the following:
    CpuCheck: Starting job with remaining CPU = 21868.7 (secs)
    CpuCheck: Job will stop when remaining CPU = 60 (secs)
    CpuCheck:Ending job with remaining CPU = 14698.97 (secs)
    
    There should also be one line per event of the form
    CpuCheck: CPU remaining = 1234.5 (secs)
    
    They are sent to ErrLogger's trace output stream. If you know how to get at it, please update the instructions here.

[Program Timing]

[Babar Home Page]

This page is maintained by Charlie Young
Email young@slac.stanford.edu