Summary
The CU is different from the LAT in many respects, so is the software to run it. There is essentially only a single local installation allowing to run the CU, right now, and it resides on the lat-btserver machine. Here are some notes about the installation itself, the tests that can be performed, the schema files to be used.
Installation
Both the LATTE and the INT releases are installed in
/usr/local/online
For the beam we had to make quite a few specific modifications to the code (both the core stuff and the subsystem scripts) to be eventually able to run a limited subset of the test scripts. Rather than modifying the released code directly, those changes live in a separate folder
/gnfs/home/glast/work/INT/DebugArea
which is prepended to the $PYTHONPATH (i.e. the system searches for hacked versions of the python files here, first, and then looks into the standard installation directory). The files living in this folder can be modified by the user glast (i.e. you don't need to be root).
Links to the relevant configuration files and test scripts also live nearby, the directory structure being the following:
/gnfs/home/glast/work/INT/repos/Schema/Calibration (CU_TEM_1.xml, CU_TEM_2.xml, CU_TEM_3.xml)
/gnfs/home/glast/work/INT/repos/Schema/DataTaking (CU_BT.xml)
/gnfs/home/glast/work/INT/Scripts/Calibration/TKR (TkrNoiseAndGain, TkrNoiseOccupancy)
/gnfs/home/glast/work/INT/Scripts/Calibration/CAL (CPT_beamtest)
/gnfs/home/glast/work/INT/Scripts/DataTaking (end2endBT)
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: 700004421 (PASSED).
- Reference run for the TKR module attached to TEM 2:
- Noise occupancy measurement (TkrNoiseOccupancy)
- Reference run for the TKR module attached to TEM 3: 700004422 (PASSED).
- 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: