Calibration Train
From GlueXWiki
Contents
Processing Overview
Job Structure
Currently, two passes are planned: One automated step, and one to produce outputs for calibration procedures that are still manual.
The calibrations/plugins that are run on each pass are:
- Pass 1
- Run as many calibrations as possible on one file
- Pass 1: RF_online
- Pass 2: HLDetectorTiming,TOF_TDC_shift
- Pass 3: st_tw_corr_auto [don't commit]
- Pass 4: HLDetectorTiming, CDC_amp, BCAL_TDC_Timing [time offsets, need to update]
- Pass 2
- Process/skim full run
- Calibrations: BCAL_attenlength_gainratio, BCAL_LEDonline, CDC_amp,CDC_TimeToDistance, FCALpedestals, FCALpulsepeak, FCAL_TimingOffsets, HLDetectorTiming, imaging, PSC_TW, PS_timing, pedestals,ST_Propagation_Time
- EVIO skims: FCAL pi0, BCAL pi0, BCAL-LED, FCAL-LED, random, sync
- ROOT skims: TOF_calib
- Other [Monitoring]: BCAL_LED, BCAL_inv_mass, imaging, p2pi_hists, p3pi_hists
- Incoming
- Tagger/PS workflow
- BCAL LED monitoring
Calibration run plan
The two priority items are to recalibrate the TOF with the its new running conditions and to verify calibrations with the new fADC250 firmware. All calibrations should be checked, in any case.
- Standalone calibrations (no forward tracking)
- ✓ RF time (Paul M.)
- Pedestals (System owners)
- BCAL Attenuation length/gain ratio (Mark D.)
- CDC time to distance (Mike S.)
- CDC gain (Naomi)
- ✓ SC timewalk (Mahmoud)
- TOF timing (Offsets/timewalks) (Beni)
- ✓ TAGM timing (Alex B.)
- ✓ TAGH timing (Nathan)
- ✓ PS timing (Nathan)
- ✓ Overall timing (rough) (Mike S./Sean)
- Full tracking calibrations
- ✓ BCAL Effective velocities (George)
- ✓ Overall timing (Mike S./Sean)
- ✓ SC Propagation time (Mahmoud)
- ✓ BCAL/FCAL pi0 calibrations (Adesh/Will M.)
All calibrations except the pi0 calibration should take no more than 1-3 2h runs of data.
Frequency
- Timing will be checked for each run. The known variations are:
- TOF (run-to-run)
- Tagger (~<day, corrected in run-to-run in the spring)
- CDC gains vary with temperature and pressure, can be averaged over a 1-2 hour run.
All other calibrations have been seen (so far) to be stable on a ~several week timescale
To-dos
-
Finish skim improvements - Automate constant -> CCDB pipeline
- Implement tracking database
Procedures
How to start a new run period
- Edit configuration file, e.g., $CALIBRATION_TRAIN/configs/data.config
- Change job name to the current run period and set resource limits
- Edit $CALIBRATION_TRAIN/template/job_wrapper.sh
- Set run period and version number
- Set up the files and directories
- e.g. python setup_run.py configs/data.config
- Create workflows
- swif create -workflow GXCalib-2017-01-pass1
- swif create -workflow GXCalib-2017-01-pass2
- Create SQLite CCDB
- $CCDB_HOME/scripts/mysql2sqlite/mysql2sqlite.sh -hhallddb.jlab.org -uccdb_user ccdb | sqlite3 ccdb.sqlite
- mv ccdb.sqlite somewhere
- Launch pass1 jobs
- python run_jobs_p1.py 2017-01 run_lists/f17.test
Calibration Outputs
RunPeriod-2017-01
Run Range | Version tag | Total # Jobs | Notes | Total Skim Size (TB) | BCAL pi0 (GB) | BCAL LED (GB) | FCAL pi0 (GB) | FCAL LED (GB) | PS Skim (TB) | TOF Skim (TB) |
---|---|---|---|---|---|---|---|---|---|---|
30274 - 30621 | ver01 | 13362 | 11.2 | 338 | 74 | 862 | 147 | 6.36 | 1.63 | |
30622 - 30959 | ver02 | 13783 | looser BCAL pi0 cuts | 23.3 | 2379 | 131 | 1703 | 297 | 12.7 | 3.36 |
30960 - | ver03 | 14869 | looser BCAL pi0 cuts | 13.4 | 1368 | 71 | 1000 | 142 | 7.47 | 1.99 |
- Skim files can be found in the following directory: /cache/halld/RunPeriod-2017-01/calib/ver01
- BCAL-LED - BCAL LED triggered events
- BCAL_pi0 - BCAL pi0 candidates
- FCAL-LED - FCAL LED triggered events
- FCAL_pi0 - FCAL pi0 candidates
- PS - PS triggered events
- random - random (out-of-time) triggered events
- sync - TS sync events
- TOF - TOF calibration ROOT skim