TOB and TEC modules are tested at UCSB using ARCS 8.0 provided by Aachen. A fault finding algorithm has been implemented into the software so that the testing process, including diagnoisis of faulty channels, is highly automated.
When a module is tested, ARCS outputs the following:
Data recorded during ARCS testing is stored in ROOT files and is easily accessed using ROOT. When testing production CMS modules, the 14 digit serial number (The number you enter when ARCS inititalizes) of the module is used as the name of the ROOT file the data is stored in. If a module is tested for the first time, the ROOT file will be created and the data will automatically go in the 'Record1' directory of the ROOT file. If a module is tested more than once, a new directory is added to the ROOT file and the data is stored there. For example, data from second test is put in 'Record2' and data from the fifth test is put in directory 'Record5'. This way there is always one ROOT file for each module and this file contains the entire testing history in directories 'Record1' through 'RecordN' where N is the total number of times the module has been tested.
An XML file is automatically created by ARCS each time a module is tested. The XML file contains much of the data stored in the ROOT File, but can be uploaded to the TrackerDB, a centralized Oracle database, so that it can be accessed by the rest of the collaboration. See the TrackerDB/Oracle Tutorial, and the page on cron jobs for the details of how XML files are uploaded.
A Module Summary file is automatically created by ARCS each time a module is tested. It is a text file containing the time & date of the test, the current at 300V and 450V, a list of the bad channels including fault flags, and the grade. It is a copy of the output you see at the end of the ARCS tests.
A Fast Test Summary file is automatically created by ARCS each time a module is tested. This file contains the results of the Fast Tests.