This page is meant to organize information about the calibration preparations and steps required for each subdetector for upcoming runs.

Previous runs:

• Run preparation Run VI (2006)
• Run preparation Run VII

 

Red means that nothing has been done for this (yet), or that this needs to continue through the run.
Blue means that the data has been taken, but the calibration task is not completed yet.
Black indicates nothing (more) remaining to be done for this task.

 

TPC

• Survey alignment information into DB (appears to be no survey data for TPC this this year)
• Drift velocity from laser runs (laser runs taken once every 3-4 hours, ~2-3k events, entire run) into DB (automated); check that it's working
• T0 calibration, using vertex-matching (~500k events, preferably high multiplicity, once triggers are in place).
• Twist calibration as soon as data starts: same data
• SpaceCharge and GridLeak (SpaceCharge and GridLeak Calibration How-To Guide) as soon as T0/Twist calibrated: ~500k events from various luminosities, for each field.
• BBC scaler study for correlation with azimuthally asymmetric backgrounds in TPC: needs several days of generic data.
• Zerobias run with fast detectors to study short time scale fluctuations in luminosity (relevant for ionization distortions): needs a couple minutes of sequential, high rate events taken at any time.
• dEdx: final calibration after run ends by sampling over the whole run period, but initial calibration can be done once TPC momentum is well-calibrated (after distortion corrections).

TPX

???

FTPC

• HV calibration performed at start of data-taking (special HV runs).
• Temperatures into DB (automated)
• Rotation alignment of each FTPC done for each field (needs calibrated vertex from TPC[+SVT][+SSD]): generic collision data

EEMC

• Timing scan of all crates: few hours of beam time, ~6 fast runs (5 minutes each) for TCD phase of all towers crates
• EEMC initial setting & monitoring during data taking: requests to process specific data will be made as needed during the run.
• Initial settings for HV: 500k minbias fast-triggered events will give slopes necessary to adjust relative gans, 2 days analysis
• Pedestals (for offline DB) from 5k minbias events, once per fill
• "General monitoring" (e.g. correlated pedestal shift) from highly prescaled minbias and zerobias events in every run.
• Beam background monitoring from highly prescaled EEMC-triggered events with TPC for at the beginning of each fill.
• Expect commissioning of triggers using EMC after one week of collisions
• Offline calibrations unnecessary for production (can be done on the MuDst level).
• "Basic" offline calibration from MIP response in 5M minbias fast events taken a few weeks into the run
• "Final" offline calibration from pi0 (or other TBD) signal requires "huge" statistics of EHT and EJP triggers to do tower-by-tower.
• Calibration codes exist, but are scattered. Need to be put in CVS with consistent paths and filenames (status?)

BEMC

• Timing scan of all crates
• Online HV calibration of towers - do for outliers and new PMTs/crates; needed for EMC triggering. Needs~5 minutes of minbias fast-triggered events (eta ring by eta ring) at beginning of running (once a day for a few days) - same runs as for EEMC.
• Online HV calibration of preshower - matching slopes. (same data).
• Pedestals from low multiplicity events from the event pool every 24 hours.
• Offline calibrations unnecessary for production (can be done on the MuDst level).
• "Final" offline tower-by-tower calibration from MIPs and electrons using several million events

PMD

• Hot Cells (~100k generic events from every few days?)
• Cell-by-cell gains (same data)
• SM-by-SM gains (same data)

VPD/TOF

• T-TOT (~3M TOF-triggered events)
• T-Z (same data)