Run preparation Run VII


There is some question as to whether certain tasks need to be done this year because the detector was not moved during the shutdown period. Omitting such tasks should be justified before skipping!

  • Survey alignment information into DB (appears to be no survey data for TPC this this year)
  • High stats check of laser drift velocity calibration once there's gas in the TPC: 30k laser events with and without B field.
  • Check of reversed GG cable on sector 8 (lasers) once there's gas in the TPC: same laser run as above
  • 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, new method from laser runs (same laser runs as above).
  • Twist calibration as soon as data starts: ~100k events, preferrably central/high multiplicity, near start of running for each field
  • SpaceCharge and GridLeak (SpaceCharge and GridLeak Calibration How-To Guide) as soon as T0/Twist calibrated: ~100k 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.
  • Need a field flip to identify origins of offsets in SpaceCharge vs. scalers as well as disentangling TPC distortions from silicon alignment.
  • 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).
  • 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
  • Pulser runs (for initial gains and alive status?)
  • Initial alignment can be done using roughly-calibrated TPC: ~100k minbias events.
  • P/N Gain-matching (any special run requirements?)
  • Alignment, needs fully-calibrated TPC: 250k minbias events from one low luminosity (low TPC distortions/background/occupancy/pile-up) fill, for each field, +/-30cm vertex constraint; collision rate preferrably below 1kHz.
  • Temp oscillation check with lasers: generic data once triggers are set.
  • Initial alignment can be done using roughly-calibrated TPC+SSD: ~100k minbias events.
  • Alignment, needs fully-calibrated TPC: 250k minbias events from one low luminosity fill (see SSD).
  • End-point T0 + drift velocity, needs fully-calibrated SSD+TPC: same low luminosity runs for initial values, watched during rest of run.
  • Gains: same low luminosity runs.
  • Timing scan of all crates: few hours of beam time, ~6 minb-fast runs (5 minutes each) for TCD phase of all towers crates, another 6 minbias runs for the timing of the MAPMT crates, 2 days analysis
  • EEMC initial setting & monitoring during data taking: requests to process specific data will be made as needed during the run.
  • Initial settings for HV: 200k 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 5 hours
  • Stability of towers from one 200k minbias-fast run 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 (still undone for previous runs).
  • Calibration codes exist, but are scattered. Need to be put in CVS with consistent paths and filenames (status?)
  • 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. Not done before, will piggyback off other datasets.
  • 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
  • upVPD (calibration?)
  • No TOF this year.