Full Run QA

This page details the current state of the full run QA for the 2009 200GeV run. The QA begins on  4/21/2009 (day 111) with run 10111030 in fill F10637 and ends on 6/29/2009 (day 180) with run 10180059 in fill F11016.

To create the prioritized run lists, I first use a tcl script to merge the 10 QA'd run lists provided by the reviewers (documented here) with a general run list. The result is a master QA'd run list. This master list is then processed by another tcl script to sort the runs into priority lists based on a set of criteria. The output is three lists: a first priority list, a second priority list, and a discard list. The format of these files are: fill, run, runtype, number of events, L2JetHigh triggers, JP1 triggers, L2BGamma triggers, ZDCMB triggers, daq files, and status codes. The script also compiles some statistics for the runs in the three lists.

The criteria for the various lists are:

First Priority:

• Must have the emc eemc and tpx detectors UNLESS the run is a zdc_polarimetry run
• Cannot have QA code Cx,Ex,Eh,Ej,Ec,Bx,Bc, or Bj
• Cannot be marked as Questionable or Bad

Second Priority:

• Can be missing the emc eemc and tpx detectors
• Can contain one or more of the above QA codes
• Can contain runs marked as Bad or Questionable

Discard:

• Runs containing the QA code Xx

Note that fmsSetupProd runs are ignored by this code; they do not appear in any of the lists nor are they counted in the statistics.

Statistics:

I counted a total of 1939 runs with 875 in the first priority list, 873 in the second priority list and 191 in the discard list. Further statistics are compiled below.

Table 1: Statistics for all runs.

Table 2: Statistics for zdc_polarimetry runs

Table 3: Statistics for runs with tpx in

The following tables display number of runs and number of events/triggers broken down by trigger setup name. The abbreviations used are:

zdc = zdc_polarimetry

Hi = production2009_200Gev_Hi

Lo = production2009_200Gev_Lo

Single = productioin2009_200Gev_Single

nocal = production2009_200Gev_nocal

noendcap = production2009_200Gev_noendcap

Table 4: The number of runs for each trigger setup name.

Table 5: The number of events and fired triggers (L2JetHigh and JP1) for each trigger setup name in the first priority run list.

Table 6: The number of events and fired triggers (L2JetHigh and JP1) for each trigger setup name in the second priority run list.