Offline Monitoring Data Validation
This page contains the procedure for checking if production runs are of good quality and can be used for physics analysis.
Run Periods
- RunPeriod-2016-02 Validation
- RunPeriod-2016-10 Validation
- RunPeriod-2017-01 Validation
- RunPeriod-2018-01 Validation
- RunPeriod-2018-08 Validation
- RunPeriod-2019-01 Validation
- RunPeriod-2019-11 Validation
Procedure
For each production run, do the following:
- Go to the | Offline Run Browser page.
- Follow the steps outlined in the checklist below.
- Certify that each section is okay
- (DB + script to be developed)
- Set run status = 1 in RCDB
- (script provided)
Run Statuses
- -1 - unchecked
- 0 - rejected (not physics-quality)
- 1 - approved
- 2 - approved long/"mode 8" data
- 3 - calibration / systematic studies
Checklist
Example Monitoring Spreadsheet
Reference run for 2017-01: 30780
Reference run for 2018-01: 40933/4
Reference run for 2018-08: 51388
Reference run for 2019-11: 71XXX
- BCAL
BCAL Notes
- CDC
CDC Notes
CDC Occupancy: There should be a uniform decrease in intensity from the center of the detector outward. Random white cells scattered throughout occur when not enough data were collected, eg empty target runs, trigger tests or no beam. Several contiguous white, dark blue or bright yellow cells which don't match the neighboring cells are a problem.
- FCAL
FCAL Notes
- FDC
FDC Notes
PS Notes
- SC
SC Notes
TAGH Notes
TAGM Notes
- TOF
TOF Notes
- RF
- Check timing offsets - Reference: [ link ]
- Should be centered around zero
- Check timing offsets - Reference: [ link ]
- Timing
- Check Calorimeter Timing - Reference: [ link ]
- Check Drift Chamber Timing - Reference: [ link ]
- Check PID System Timing - Reference: [ link ]
- Check Tagger Timing - Reference: [ link ]
- Check Track Matched Timing - Reference: [ link ]
- Check Tagger/RF Timing - Reference: [ link ]
- Check Tagger/SC Timing - Reference: [ link ]
Timing Notes
- Analysis
Analysis Notes