...
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.
Patrick will back-up all data from the computers. Reference runs for data taking were not linked because we are not connected to the farm (behind firewall).
No modifications were done or rework on towers during the beam test. During intergration for 1 x 4 one TKR connector for cable 7 of non-flight TKR, slightly shifted and we added a connector saver to avoid stress in the cable.
No anomalies or failures were experience over the coruse of the beam test that would degrade the flight hardware.
Clearance is very small, exercise care before remving the Inner Shiopping Container.
Flight Hardware : TKR (FM8) & CAL (FM101) on bay 3 (close to the edge) and CAL (FM109) on bay 1.
...
Here is the list of functional tests we performed as part of the incoming procedure. Charge injection tests are done one tower at the time.
There is no TKR module 1 so in LATTE do not power on this tower otherwise you will get errors.
For charge injection runs, tests are self-contained and results labeled PASSED are meaningful. Charge injection tests are done one tower at the time.
For data taking tests we added a reference taken from the Beam Test at CERN (see below) because PASS/FAIL condition is affected by how we treated the FIFO errors. Also configuration of the set-up may affect rates. So the figure of meirt for the data taking is that event rates are consistent with expectations.
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*)
...