Difference between revisions of "Calibration Challenge"
From GlueXWiki
(Created page with "__TOC__ = Overview = We propose to run a "Calibration Challenge" starting the first week of December 2015. The goal will be to take a run with zeroed out calibrations and...") |
(→Types of Data) |
||
| Line 27: | Line 27: | ||
* [[Automated Timing Calibrations]] | * [[Automated Timing Calibrations]] | ||
* [[Spring 2015 Dataset Summary]] | * [[Spring 2015 Dataset Summary]] | ||
| + | |||
| + | The largest spring production run is 2931, so that would be a good choice. It has the following charateristics: | ||
| + | * 50um diamond radiator | ||
| + | * 800A solenoid current | ||
| + | |||
In principle, simulations could be used as well. Some effort is needed to work on the software to support this. | In principle, simulations could be used as well. Some effort is needed to work on the software to support this. | ||
| + | |||
| + | = Calibration Classes = | ||
| + | |||
| + | We can classify the calibrations by the type and amount of data needed. | ||
| + | Only tables that have well-defined procedures have been included. | ||
| + | |||
| + | == One Run Photon Beam Data == | ||
| + | |||
| + | * All/base_time_offets | ||
| + | * CDC/timing_offsets | ||
| + | * FCAL/timing_offsets | ||
| + | * START_COUNTER/adc_timing_offsets | ||
| + | * START_COUNTER/tdc_timing_offsets | ||
| + | * START_COUNTER/timewalk_parms | ||
| + | * TOF/adc_timing_offsets | ||
| + | * TOF/tdc_timing_offsets | ||
| + | * TOF/... | ||
| + | * PHOTON_BEAM/RF/time_offset | ||
| + | * PHOTON_BEAM/RF/time_offset_var | ||
| + | * PHOTON_BEAM/RF/time_resolution_sq | ||
| + | * PHOTON_BEAM/hodoscope/fadc_time_offsets | ||
| + | * PHOTON_BEAM/hodoscope/tdc_time_offsets | ||
| + | * PHOTON_BEAM/microscope/fadc_time_offsets | ||
| + | * PHOTON_BEAM/microscope/tdc_time_offsets | ||
| + | |||
| + | Future: | ||
| + | |||
| + | * Most basic FDC calibrations? | ||
| + | |||
| + | == Multiple Run Photon Beam Data == | ||
| + | |||
| + | * FCAL/gains | ||
| + | * START_COUNTER/attenuation_factors | ||
| + | * START_COUNTER/propogation_speeds | ||
| + | |||
| + | Future: | ||
| + | |||
| + | * CDC/wire_aligment ? | ||
| + | |||
| + | == Cosmic Data == | ||
| + | |||
| + | * CDC/cdc_drift | ||
| + | * CDC/wire_aligment | ||
| + | * CDC/sag_parameters | ||
| + | * CDC/drift_parameters | ||
| + | |||
| + | |||
| + | = Challenge Type 1 = | ||
| + | |||
| + | The following plugins will be used: | ||
| + | * BCAL_TDC_Timing | ||
| + | * HLDetectorTiming | ||
| + | * PSC_TW | ||
| + | * <span style="color: red">SC timewalk [upcoming]</span> | ||
| + | * <span color=red>TAGH timewalk [upcoming?]</span> | ||
| + | * <span color=red>TAGM timewalk [upcoming?]</span> | ||
Revision as of 18:51, 27 October 2015
Contents
Overview
We propose to run a "Calibration Challenge" starting the first week of December 2015.
The goal will be to take a run with zeroed out calibrations and to see how many calibrations can be automatically extracted.
Test runs will be performed in the weeks leading up to this challenge.
Types of Tests
Various types of tests could be run to exercise our calibration procedures.
- Calibration values are normalized to some neutral value (e.g. 1 or 0), and the calibrations are derived "ab initio".
- Given the diversity of run conditions among the few production runs in the spring data, it makes sense to do this test with just one run at a time, and not combine runs. Therefore, we can test calibrations that only need ~1 runs' worth of data.
- Current calibration values are perturbed by some amount, and procedures are run to see how well the current values are recovered.
- The perturbations would be specific to each calibration. Different functional forms? Gaussian? Square wave?
- This would give us a way of testing calibrations that require more than one run's worth of data to be done from an uncalibrated state.
Types of Data
References:
The largest spring production run is 2931, so that would be a good choice. It has the following charateristics:
- 50um diamond radiator
- 800A solenoid current
In principle, simulations could be used as well. Some effort is needed to work on the software to support this.
Calibration Classes
We can classify the calibrations by the type and amount of data needed. Only tables that have well-defined procedures have been included.
One Run Photon Beam Data
- All/base_time_offets
- CDC/timing_offsets
- FCAL/timing_offsets
- START_COUNTER/adc_timing_offsets
- START_COUNTER/tdc_timing_offsets
- START_COUNTER/timewalk_parms
- TOF/adc_timing_offsets
- TOF/tdc_timing_offsets
- TOF/...
- PHOTON_BEAM/RF/time_offset
- PHOTON_BEAM/RF/time_offset_var
- PHOTON_BEAM/RF/time_resolution_sq
- PHOTON_BEAM/hodoscope/fadc_time_offsets
- PHOTON_BEAM/hodoscope/tdc_time_offsets
- PHOTON_BEAM/microscope/fadc_time_offsets
- PHOTON_BEAM/microscope/tdc_time_offsets
Future:
- Most basic FDC calibrations?
Multiple Run Photon Beam Data
- FCAL/gains
- START_COUNTER/attenuation_factors
- START_COUNTER/propogation_speeds
Future:
- CDC/wire_aligment ?
Cosmic Data
- CDC/cdc_drift
- CDC/wire_aligment
- CDC/sag_parameters
- CDC/drift_parameters
Challenge Type 1
The following plugins will be used:
- BCAL_TDC_Timing
- HLDetectorTiming
- PSC_TW
- SC timewalk [upcoming]
- TAGH timewalk [upcoming?]
- TAGM timewalk [upcoming?]
