Difference between revisions of "RunPeriod-2019-11 Validation"
From GlueXWiki
(→Calibration/Tuning) |
(→Calibration/Tuning) |
||
Line 21: | Line 21: | ||
== Calibration/Tuning == | == Calibration/Tuning == | ||
− | * Calibration: 71336 | + | * Calibration: |
+ | ** AMO: 71336, 71344 | ||
+ | ** Diamond: 71345, 71346, 71347 | ||
+ | ** bad PS settings? it looks like it might be okay, but Sasha said readout thresholds should be optimized | ||
+ | * Raw mode: 71337 | ||
+ | ** short raw mode runs: 71338-71343 | ||
+ | |||
+ | Arbitrarily end it here and start production counting. The diamond runs could potentially count as production? | ||
== Physics Production Runs == | == Physics Production Runs == |
Revision as of 23:16, 12 January 2020
December 2019 Run
- Straight track runs: Starting around 70652, until 70786
- TOF/CDC HV scans: 70817 - 70828
- Initial commissioning runs (not everything read out): 70829 - 70834
- DIRC commissioning runs (no PS): 70835 - 70892
- Bad TOF HV: 70874 - 70892
- Lost data: 70850 - 70895
- TRD/GEM data: 70959 - 70963
- 2nd round of DIRC commissioning runs (better TOF HV, rocfcal1 restored): 70967-
- raw mode tests with updated ST firmware: 70995 - 71000
- production mode with updated ST firmware: 71002 -71206 (?)
- more firmware fixes on part of the FCAL: 71207 -
2020 Run
Calibration/Tuning
- Calibration:
- AMO: 71336, 71344
- Diamond: 71345, 71346, 71347
- bad PS settings? it looks like it might be okay, but Sasha said readout thresholds should be optimized
- Raw mode: 71337
- short raw mode runs: 71338-71343
Arbitrarily end it here and start production counting. The diamond runs could potentially count as production?