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

BbkDatasetHistory

Datasets can evolve over time, as new collections are processed; or occasionally as old ones are determined to be bad. This evolution can be listed with the BbkDatasetHistory command. For a recent version, use release 14.4.0c or later.

General Options

site  user  dbname  localdsprefix  debug  verbose 

Specific Options

no options  datasets 

Advanced Connection Options

dbtype  dbserver  dbdriver  dbpass 

Note you can use this options to connect to a database or you can create a 'site' with these connection options. Here BbkConnect to find out more.

Specific Options

no options

Like for BbkDatasetTcl running BbkDatasetHistory with no options returns a list of dataset names.

    % BbkDatasetTcl
    % BbkDatasetTcl: 3 datasets found:-
    % AllEventsRun3Conv
    % GridKa.32955-36172
    % ...

Most of the dataset names should be self-explanatory. For SP datasets, you can use BbkSPModes to determine the relevant "mode numbers" and other information.