From the spin QA we found out where on the physical RHIC ring the blue and yellow beams collide the first bunches (bunch zero). Then we determined which bunches are colliding at STAR. Bunch crossing QA will tells us if the beams are offset from one another at the STAR collision point.

This process begins by running TestChain.C over all of the files on disk. This will create the bX7 and bX48 spectra for the run up to a maximum of 10,000 events. It also outputs an "ideal" histogram that is created from the spin database beam crossing. For instance the v124 files that are uploaded include a header that is either "0 240" or "0 120" depending on the first bunch collision point. For 2013, this header says "0 240" which means bunch zero of Yellow Beam (YB) and bunch zero of Blue Beam (BB) collide at 2 O'clock and 8 O'clock on the RHIC beam. Thus the ideal histogram is created so that the abort gaps for BB and YB are in the appropriate places .


********************
Procedure:

1) obtain a run list of produced runs :
get_file_list.pl -cond "filetype=daq_reco_MuDst,filename~st_W,production=P14ia,trgsetupname=pp500_production_2013,storage=nfs" -keys "orda(runnumber)" -distinct -limit 0

1010  of p14ia production used in this analysis

2) Find the offset between the beams 
           a)  Run the macro TestChain.C over all of the files on disk and create bX7 and bx48 spectra for the run up to a maximum of 10,000 events. This also create an "ideal" histogram which reflect abort gaps for BB and YB are in the appropriate places ,  using the database info for beam crossing. For instance the v124 files that are uploaded include a header that is either "0 240" or "0 120" depending on the first bunch collision point. For 2013, this header says "0 240" which means bunch zero of Yellow Beam (YB) and bunch zero of Blue Beam (BB) collide at 2 O'clock and 8 O'clock on the RHIC beam .  

           bx7:                                                                                                           bx48:              

   

                                                                                            
                             
           b) Slide an ideal histogram over the bx spectrum to find the beam offset values of both bx7 and bx48  for each run.

           c)  Run a different macros through the produced offset table as a function of run number to see the runs with non zero offset.

Run number Vs beam crossing offset for bx7 and bx48 :

  
            Out of 1010 runs we found 2 runs with different offset R 14117001 (bx7 offset   ) and R14118062 (bx7 offset  ) . Found these 2 runs have neglegible luminosity and decided to mark them as baf and exclude from the run list.

Now looking at the chi2 minimum profile found that 6 fills have higher chi2 minimum values. By Investigating turned out that these 6 fills contains unintended missing bunches. These has beem confirmed by checking cdev records of intended/ measured fills patterns for both beams

DB uploding:

To DB records,

Uploading mask tables:
http://www.star.bnl.gov/protected/spin/balewski/2005-spinDB/expert.html

mysql -h dbx.star.bnl.gov --port 3316 Calibrations_rhic -e "select beginTime,endTime from spinBXmask where beginTime>'2013-03-17 04:40:00' and beginTime<'2013-05-06 09:10:00' order by beginTime"

goodRunList

spinpwg
slides

F17318