Home » Groups » STAR Protected

Run 13 QA Initial p+p at 500 GeV.

Updated on Tue, 2013-06-11 09:44. Originally created by dolv719 on 2013-06-11 09:43.

Run 12 QA Notes Page: http://drupal.star.bnl.gov/STAR/blog/jkadkins/2013/may/17/run-qa-run12-200gev-p-p-data

 
Notes in the "passes" are from Run12_EventQA_Notes.pdf, which can be found in the link above.
 
Kevin/Jim: Is there some code that I can look at and modify?

This is what I found relevant from Kevin's Notes.  Any input is welcomed.

 
Used MuDST files directly and produced plots:
  • EEMC/BEMC transverse energy (E) and tower multiplicity 

  •  Track transverse momentum (pT) and multiplicity for leading and second order vertices

  • X, Y, and Z vertex locations for leading and secondary vertices  

1st Pass:

Also need a list of relevant triggers for "good" runs to include:
     Initial List (My Best Guess)
  • BBCMB
  • ZeroBias
  • ZDCMB
  • VPDMB
  • MB-Base
  • JP0
  • JP1
  • JP2
  • JP2*L2JetHigh
  • JP1*DiJet
  • JP0*DiJet
  • BAJP

Use the following to investigate the runs with the above triggers

  • Log Browser
  • Shift QA plots
  • DAQ rates
  • Shift log
  • Dead time
  • Minimum event threshold???

Is there a work schedule log?  When triggers, detectors etc. were undergoing testing.

 
2nd Pass:

 
The method (aside from those which stick out clearly) will be to fit the plots with a constant polynomial. Then from this fit we extract the mean and RMS (i.e.σ2) value, and we assert that the value for that run must fall within 2σ, otherwise it will be investigated as a bad run.

Seems to work mostly with level 2 plots
     Which ones? L2Jet and L2JetHigh?
  • Hot towers

3rd Pass:

 

Now look at the trackpTfrom the leading order vertex to make cuts with. Again I 

will get the average for each trigger and then use an interval defined by 2 times the RMS 

value (2σ) to define suspicious runs.
 
4th Pass:
 
Investigate end cap and BEMC spectrum



 

Groups: