Last modified: 17 February 1999

Where to find the data:

 

$BFROOT/data/data03/dcdata/dch

This is where you can find the data files. Files are named runnnn.xtc-new where nnn is the run number.

The data files are copied to this NFS directory before being written to the tape.

Interesting data are kept here as long as the space allows, while junk runs are erased after copying to the tape.

Run Information

Information on runs, ntuples and calibration files can be found using the runinfo utility. Define an alias like alias runinfo "$BFROOT/data/data03/dcdata/dch/runinfo". Then run runinfo with a run number as the first parameter.

Tape in the silo

The data are written to a tape in the silo for archiving. The tape can be read from SLAC server machines (e.g. morgan and percheron) using stagein command.

How to stagein:
The easiest and recommended way is:

cd $BFROOT/data/data03/dcdata/dch

revive runXXX

The script revive will send a correct request to the staging system, which will read in the data to a staging disk and create a symbolic link runXXX for you. Don't mind if the link is already there, or if the data itself is there: revive and stagein will (at least should) take care of all the details.

Calibration Run Numbers:

The calibration run numbers associated with each data run are the last calibrationn run taken before the data run. This does not mean that the calibration run was validated and so you may need to use an earlier calibration run.

 

How to analyse the data:

Look at the tutorial  here.

 

Runs 2161 to 2292:

The calibration (T0 and charge) for these runs  is incorrect. To get the correct values you need to run using the presciption described here.

Dataflow 2 data: Runs 1945 to 2140

Dataflow 3 data: Runs 2143 and beyond

Integrated data: BaBar Runs 1 and beyond

For comments, questions or changes to this page contact Fergus Wilson