Thank you very much Kevin Adkins, for providing me all the necassary documents for spin QA and giving me nice clear explanatory answers for  all of my  questions!!!!!!!!!!!!!!!!!!!!!!

*********************************************************************************************************************************

This document outlines both the QA and database upload operations. From the spin QA we find out where on the physical RHIC ring the blue and yellow beams collide the first bunches (bunch zero). We then use code to decide which bunches are colliding at STAR. This is important because in analysis we want to know the orientation of the spin for each bunch that is colliding at STAR. This QA, coupled with the spin patterns from spin QA tell us precisely this. 

1) Spin QA
 This process is one in which we query the cdev database after a run and determine if the spin information  is correct, and if this pattern is maintained throughout an entire  We then take certain information and load it to a database. 

   a) SpinQA process:  https://drupal.star.bnl.gov/STAR/system/files/SpinQA_HowToFinal_0.pdf
   b) Uploading to database :  https://drupal.star.bnl.gov/STAR/system/files/dbUpload_HowTo.pdf


2) bXing QA
 To decide if the beams are offset from one another at the collision point. This is done AFTER production of the MuDst's and then  use to create the histograms necessary.

**********************************************************************************************************************************************************

Step ONE:   Produce the run list using the script  loopMainAll.tcl 

 Produce a run list as a First Priority run list with the similar requirement used for runQA , from March 15- June 10 :  FP1.csv

Step TWO:  Perform spin QA using spbitSeeker.tcl

spbitSeeker  qurry the CDEV data base to get the  spin info of each fill two times, at the begining and end of the fill.

below is the command use to get the spin info from the data base.

mysql -h dbbak.starp.bnl.gov --port 3412 Conditions_rhic -e "select dataS from kretDbBlobS where nodeID=9 and beginTime>'2013-03-24 04:09:35' order by beginTime limit 1" -s -E
mysql -h db04.star.bnl.gov --port 3412 Conditions_rhic -e "select dataS from kretDbBlobS where nodeID=9 and beginTime>'2013-03-24 04:09:35' order by beginTime limit 1" -s -E
 
spbitSeeket produce two output files called  v124 files  per fill which records the blue and yellow beam polarization for each 360 time bucket at the begining and end of the fill.

More Info about v124 files

spbitSeeker also produced a text file called spinTime.txt which contains some spin info such as number of filled bunches of Yellow and Blue beams, Polarization pattern of each beam which repeats after every 8 filled bunches and if any errors in the pattern, etc,, of each fill.

More info about spinTime.txt

 Problems encountered during step 2:

 a)  In the spinTime.txt for Fill 17232 to  Fill 17250 Polarization pattern was not as expected.
 b)  Code break and stop runnning at the Fill 17538.

-------------------------------------------------------------------------
To Solve a) Kevin contacted Elke,

She recall that the Spin patterns has changed for run 13 compared to run 12  and infact changed twice due to CAD error. 
Elke's slides presenting spin petterns of run 13:
 https://www.phenix.bnl.gov/WWW/publish/elke/STAR/TALKS/eca-spinpatterns2013.correction.pptx

Spin patterns has changed on March 21st.

So spin Pattern begining of run 13 to March 21st has modulo 14, means spin pattern repeats after every 14 bunches.

Spin Pattern of run 13 starting from  March 21st 2013 has modulo 8