Difference between revisions of "Offline Monitoring Data Validation"
From GlueXWiki
(→Procedure) |
|||
| Line 15: | Line 15: | ||
* Set run status = 1 in RCDB | * Set run status = 1 in RCDB | ||
** (script provided) | ** (script provided) | ||
| + | |||
| + | === Run Statuses === | ||
| + | |||
| + | * -1 - unchecked | ||
| + | * 0 - rejected (not physics-quality) | ||
| + | * 1 - approved | ||
| + | * 2 - approved long/"mode 8" data | ||
= Checklist = | = Checklist = | ||
Revision as of 18:16, 22 March 2016
This page contains the procedure for checking if production runs are of good quality and can be used for physics analysis.
Run Periods
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
Checklist
- BCAL
- Check ...
- CDC
- Check ...
- FCAL
- Check ...
- FDC
- Check ...
- PS
- Check ...
- SC
- Check ...
- TAGH
- Check ...
- TAGM
- Check ...
- TOF
- Check ...
- RF
- Check timing offsets - Reference: [link]
- Should be centered around zero
- Check timing offsets - Reference: [link]
- Timing
- Check Track Matched Timing - Reference: [link]
- Check Tagger/RF Timing - Reference: [link]
- Check Tagger/SC Timing - Reference: [link]
- Analysis
- Check ...
