2009 Spin QA: 200GeV

On this page I detail the procedure used for doing the spin QA. I also list the steps I have taken to fix fills that had inconsistent spin data in the cdev database.

Method:

First, I query the cdev database and compile a list of runs (runlist) spanning a desired time range. This is done with the script loopMainAll.tcl. This script records the fill number, trigger setup name, shift status, which detectors where in, as well as several trigger quantities for each run. The script automatically excludes runs less than a minute as well as runs with certain trigger setup names (ie runs containing ped or pulse).

After the runlist is generated, it is analyzed using the script spbitSeeker.tcl which collects information about each fill, including start/stop times, number of runs in the fill, number of bunches, and spin bunch pattern. For each fill, the script also records the spin bunch pattern for the first and last run and puts them in seperate files.

Finally, a script called begEndComp.tcl is run, which compares the spin patter in the first and last run of each fill. It is assumed that the spin bunch pattern is stable throughout the course of a fill, so if the patterns match in the first and last run, the fill is considered to have a known bunch pattern and is put in the good list. If, however, the patterns do not match, the fill is flaged and put into the bad list. I then take a closer look at each fill on the bad list. Using a combination of runlog entries, RICH scalar information, and cdev queries, I try to determine which runs are causing the spin pattern mismatch. I then remove those runs from the runlist manually and repeat steps two and three until all fills have consistent spin bunch patterns.

The original runlist I generated spanning Fill 10637 through Fill 11016 (4/21/09 - 6/30/09) is here.

The list of fills with consistent spin data in the first and last run is here.

The list of fills with inconsistent spin data in the first and last run is here.

Note: In the description of the spin bunch pattern some spaces contain the letter 'e' or 'c'. These occur only when the number of bunches is less than 100. An 'e' was used if the bunch(modulo 8) was consistently empty while a 'c' was used if a bunch(modulo 8) was filled more than once but with different spin states. These fills should not be placed with fills with patterns P1-P4 for systematic purposes. For more detail see Jim's 2006 spin pattern page.

Due to the large number of bad fills (~80) I have broken the bad fills into 4 groups based on type of error. In the first group I remove all bad fills containing two or fewer runs. In the second group I fix the fills having the error code *fe. In the third group I fix the fills having the error code *fb. In the last group I fix the bad fills which had no error code (as well as one fill with error code *s).

Group 1:

Table 1: This table contains the runs I had to remove from group 1 to get a consistent spin pattern. Also listed are fill number, run type, and status.

Group 2:

Table 2: This table contains the runs I had to remove from group 2 to get a consistent spin pattern. Also listed are fill number, run type, and status.

Group 3:

Table 3: This table contains the runs I had to remove from group 3 to get a consistent spin pattern. Also listed are fill number, run type, and status.

Group 4:

 Table 4: This table contains the runs I had to remove from group 4 to get a consistent spin pattern. Also listed are fill number, run type, and status.

Summary:

In total, 80 fills started with inconsistent spin information. I had to remove 122 runs to fix the fills.

• 95 runs were fmsSetupProd runs. These runs often came before beam was injected and so had undefined spin patterns
• 13 runs were zdc_polarimetry runs. The zdc_pol runs which were bad often came very close to injection or beam dump.
• 11 runs were production runs. More effort should go into understanding why these runs had bad spin pattern information
• The last three runs were pp2pp or test runs.

The final runlist after the corrections listed above can be found here.

The final list of fills with consistent spin data can be found here.

All fills have been fixed, so there is no list of bad fills.