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 - latbt01 machines. Here are some notes about the installation itself, the tests that can be performed, the schema files to be used.
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: run 700004421 (PASSED)
- Reference run for the TKR module attached to TEM 2: run 700004435 (PASSED*)
* Note that TKR FM16 (connected to TEM 2) is not filght and it does have its "features" and idiosyncrasies. In particular there are quite a few layers failing in terms of disconnecetd/defecting channels (Y15, X13, Y11, Y10, Y2). A good reference run for comparison (though quite old, now, and taken with a different software version) is run 700000107:
- Noise occupancy measurement (TkrNoiseOccupancy)
- Reference run for the TKR module attached to TEM 3: run 700004422 (PASSED)
- Reference run for the TKR module attached to TEM 2: run 700004436 (PASSED)
CAL
- Standard CPT (CPT_beamtest.py)
- Reference run for the CAL module attached to TEM 3: runs 700004423-700004433, summary 700004434 (PASSED)
- Reference run for the CAL module attached to TEM 2: runs 700004437-700004447, summary 700004448 (PASSED)
- Reference run for the CAL module attached to TEM 1: runs 700004449-700004459, summary 700004460 (PASSED)
Data taking
- Standard end2end (BT 2, nominal conditions, all triggers enabled).
- ~100 kevents: run 700004461.
Installation
Both the LATTE and the INT releases are installed onto lat-bt01 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.
Data live either in:
/gnfs/data/DVD
or:
/gnfs/data/LATTE
depending on the time of collection.
The end2end data taking configurations are listed here.