Difference between revisions of "Calibration Train"
From GlueXWiki
| Line 1: | Line 1: | ||
__TOC__ | __TOC__ | ||
| − | + | = Processing Overview = | |
| − | + | * [[Old Calibration Train]] | |
== Job Structure == | == Job Structure == | ||
| Line 65: | Line 65: | ||
# Implement tracking database | # 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 | ||
| + | #* Launch pass1 jobs | ||
| + | #* python run_jobs_p1.py 2017-01 run_lists/f17.test | ||
Revision as of 00:25, 10 February 2017
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
- Launch pass1 jobs
- python run_jobs_p1.py 2017-01 run_lists/f17.test
