SetA QA

I am attempting to do a dijet analysis on the 2009 200GeV data found in the trigger data block. Hopefully analyzing the trigger block data, which has no tracking information, will help identify issues which will arise in an analysis of the fully produced data at foreward regions where tracking from the TPC dies out. The first step in analyzing the trigger block data is identifying good runs. This page documents my QA efforts for a subset of the 2009 200GeV runs.

The runlist detailed on this page contains 234 runs and can be found here. This list was created from the full list of 200 GeV runs used to make the prioritized lists for full production. I modified the sorting script so that the first priority list contained only production runs with both the emc and eemc in and without the error codes Ex, Eh, Ej, Ec, Bx, Bc, and Bj. To create the above runlist I used the first priority list described above and took only production2009_200Gev_Single runs which had a QA code of Ok.

I have created a set of plots for these runs similar to those which would be found on the L2Jet online monitoring pages. These monitoring plots can be found here.

In addition to the monitoring plots I have ploted the ratios of several quantities as a function of run. Some of these quantities include number of events, number of various triggers, number of towers fired, and transverse energy deposited in the detector. I then look at the stability of these ratios over the course of the runlist and can eliminate runs which show odd behaviour. These QA plots can be found here.