...
Essentially you want to use end2endBT for data taking (and CU_BT.xml as the configuration file) while the charge injection tests must be performed for each module separately using the CU_TEM_xxx.xml files. Note that both the TKR and the CAL modules for the tower under test are declared in the schema file and must be powered on. When you press "select application" in the RunControl main gui you are automatically redirected into /gnfs/home/glast/work/INT/Scripts/DataTaking. Go one level up and then select Calibration to have access to the subsystem level calibration scripts.
Tests
...
Here is the list of functional tests we performed as part of the incoming procedure.
TKR
- Noise and gain measurement (TkrNoiseAndGain.py)
- Reference run for the TKR module attached to TEM 3: 700004418
- Reference run for the TKR module attached to TEM 2:
- Noise occupancy measurement (TkrNoiseOccupancy)
- Reference run for the TKR module attached to TEM 3:
- Reference run for the TKR module attached to TEM 2:
CAL
- Standard CPT (CPT_beamtest.py)
- Reference run for the CAL module attached to TEM 3:
- Reference run for the CAL module attached to TEM 2:
- Reference run for the CAL module attached to TEM 1:
Configuration files
add stuff