Runlist

External ASCII input to the uDST production program

This document contains the details about many external ASCII files used in the uDST production program. These files are located in the runlist subdirectory.

---

the "logbook" subdirectory

This directory contains the logbook data quality information which is placed into the uDSTs. During a production, the information for runs in the particular fill is grapped from the logbook_list.txt file by the prepare_runlist.sh script and placed into the runs.dat file. Later, the uDST production program then reads the later file and puts this information into the appropriate fields in the g1Quality table.

logbook_list.txt	-	extracted from the logrun.new file by the new_logbook_runlist_maker.pl perl script, this file contains the logbook data quality information which is placed into the uDST iExpment, iExpMode, and iExpTarg fields of the g1Quality table.
logrun.new	-	the logbook data quality file maintained by the shift crews. For each run, this file contains one line whose contents are: column 1 - run number column 2 - analyseable flag where: 0 - unanalyseable 1 - analyseable for physics 2 - analyseable for calibration/detector checkout column 3 - target mode where: 0 - unpolarized 1 - ? 2 - 2-state mode (RHX) 3 - 3-state mode (AHX) 4 - 4-state mode (EHX) 5 - ? 6 - ? 7 - ? 8 - ? column 4 - target gas where: 0 - empty target 1 - hydrogen 2 - deuterium 3 - helium-3 4 - helium-4 5 - nitrogen 6 - krypton 7 - mixed

---

the "production_problems" subdirectory

Located in the runlist subdirectory, this directory contains the lists of runs which, because of production problems, should not have uDSTs produced for each main (hrc) production. The files of so-called rejected runs are stored in this directory in subdirectories labelled by the main (hrc) production, e.g. 97b. The file is:

rejected.runs	-	on each line, the fields are: run number reason for removal

In practice, these runs are removed from the production by the setup_production script.

---

the "beam" subdirectory

The beam polarimeter runlist information consists of two files located in the runlist subdirectory of a production. These files are:

tpoldq.dat	-	on each line, the fields are: run number data quality flag, where: 0 = analyseable 1 = not analyseable 2 = analyseable but required significant calibration corrections the information in this file is used to fill the g1Quality_Beam field. NOTE: This file is only available for the 1996 uDST production because, for all other productions, the beam polarimeter data quality is incorporated into the calibrated polarization value by setting this value to -1.0.
info_source.fill	-	on each line, the fields are: fill number "best choice" for the beam polarization measurement where the implemented choices are: TPOL_RAW, TPOL_CALIB, and LPOL_RAW the information in this file is used to set the source for the "best" polarization measurement. This flag determines which beam polarization measurement is placed into the rPol, rPolErr, and rPolSystErr fields of the g1Beam table. In addition, so that analyses codes know the source for these fields, this information is coded into the bProdMethod field of the g1DAQ table.

---

the "target" subdirectory

The external target information for the uDST production is stored in two files located in the runlist/target subdirectory of a production. These files are:

runlist	-	the data quality information from an offline analysis performed by Mark Sutter. Each line contains the following fields: run number, # of bursts in run, # of bursts unpolarized target, # of bursts polarized target, # of bursts unpolarized H2, # of bursts unpolarized D2, # of bursts unpolarized He3, average target magnet setting (in mA), Presently, this information is used to determine the iGasType field of the g1Quality table. This information, however, is no longer necessary because the uDST production program now performs this offline analysis and places the results in the iGasType field of the g1Unpol table. Since there were mixed gases a few runs, the information in g1Unpol table is more reliable than the information in the g1Quality table. NOTE: This file is only available for the 1996 uDST production because, for all other productions, this information was pulled directly from the fillfiles by the uDST production program.
info_source.fill	-	the information in this file determines the source for the target polarization information placed into the rPol, rPolErr, and rPolSystErr fields of the g1Target table. The file has one line per fill and the fields on this line are: fill number the "best choice" for the target polarization measurement where the implemented choices are: RAW_BRP, CALIB_BRP, CALIB_PCP, CALIB_TOM, CALIB_BEST95, and EXTERNAL_ASCII In order for analysis programs to know the source for the target polarization fields, this information is coded into the bProdMethod field of the g1DAQ table.

---

the "trd" subdirectory

In the uDST production, the trd data quality is extracted by the prepare_runlist.sh script from the trd_goodlist.dat file located in this directory. This information is put into the iTRDdq field of the g1Quality table. The file contains one line for each run; the format of this line is:

1. the run number

2. the trd data quality information where: value top DQ bottom DQ 0 bad bad 1 good bad 2 bad good 3 good good

---

the "cerenkov" subdirectory

In the uDST production, the cerenkov data quality is extracted by the prepare_runlist.sh script from the cerenkov_goodlist.dat file located in this directory. This information is coded into the bCereDQ field of the g1Quality table. This file contains one line for each run; the format of this line is:

column 1	-	the run number
column 2	-	the cerenkov DQ for the top detector 1 = analyseable 0 = not analyseable
column 3	-	the cerenkov DQ for the bottom detector 1 = analyseable 0 = not analyseable

---

the "calo_thresh" subdirectory

At present, the source for the calorimeter threshold setting which is put into the rCaloThresh field of the g1Quality table depends upon the data year. For 96 data, this information was extracted by the prepare_runlist.sh script from the calo_thresh.lst.formatted file provided by Kevin McIlhany and stored in this directory. This file contains one line for each run; the format of this line is:

column 1	-	the run number
column 2	-	the calorimeter threshold (in GeV)

NOTE:	For all of the data productions except 96b, the calorimeter threshold is extracted from the CaloThreshold slow control table. So, this file is essentially obsolete.

---

the "vc" subdirectory

Starting with the 97b1 production, the VC data quality information is now available in the uDSTs. The VC group provided a list of runs which affected by various problems. Each problem was assigned a bit in a data word and then, via the vc_dq_maker.c program, a list was generated with the VC data quality for the running period. This list is stored in the file vc_goodlist.dat. The format of this file is:

column 1	-	the run number
column 2	-	the VC data quality word

At present, the VC data quality for the 1997 dataset (the only year for which this information exists) is encoded into this field as follows:

= 0	:	all unmentioned runs	-	all is fine with the VCs
0x01	:	runs 16383 thru 16841	-	the VC readout was out of sync with the rest of the DAQ readout, so the VC data is not useable. For this reason, these runs were reconstructed with only the NOVC (forced-bridge) tracking method.
0x02	:	runs 18079 thru 18158	-	1 top and 1 bottom X plane in the VCs have lower than nominal efficiency (by around 4%) due to improper timing of the readout. This problem, based upon offline analysis, does not impact the number of tracks found by the standard reconstruction.
0x04	:	runs 20790 thru 20980	-	the VC readout was occasionally out of sync with the DAQ for periods of time no longer than a burst. This problem reduces the ratio of tracks found by the the standard and forced-bridge (NOVC) reconstructions methods from 1.0 to 0.95
0x08	:	runs 24438 thru 24537	-	1 top V plane, 1 top U plane, and 1 bottom V plane in the VCs were operating at an incorrect voltage. This reduced the ratio of tracks found by the two reconstruction methods from 1.0 to 0.97.
0x10	:	runs 18080 thru 20740 runs 26290 thru 26539 runs 26642 thru 26807	-	1 bottom X-wing plane was turned off due to HV trips. This problem does not reduce the ratio of the tracks found by the two reconstruction methods.
= -1	:		-	no VC data quality information available for this run

As with all run-level data quality, this information is fetched by the prepare_runlist.sh script and eventually is placed into the bVcDQ field of the g1Quality table by the uDST production program.