-
Notifications
You must be signed in to change notification settings - Fork 2
/
ch4-analysis.tex
41 lines (26 loc) · 1.4 KB
/
ch4-analysis.tex
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
\chapter{Analysis}
The analysis encompasses data taken during the 2005 and 2006 RHIC runs when
the polarized proton beams were longitudinally polarized and colliding at a
center-of-mass energy of 200 GeV. Spin asymmetries are constructed using
charged pions produced at mid-rapidity and having large transverse momentum.
\input{ch4-01-equations}
\input{ch4-02-polarizations}
\input{ch4-03-lumi}
\section{Spin-Sorted Yields}
\input{ch4-04-data-selection}
\section{Systematic Uncertainty Evaluations}
\input{ch4-06-polarization-vectors}
\input{ch4-07-pt-shift}
\input{ch4-09-syst-trig}
% \subsection{Polarization Vectors and Transverse Asymmetries}
% data selection - 1/2 day
% pion identification - 1 day
% jet reconstruction - 1 day
% jet/pion correlations - 1/2 day. Just a plot of the dphi matching in data and simulation ought to be enough.
% Systematic Uncertanties
% nothing for PID, but will i need to redo the run 6 analysis to subtract backgrounds? yes. Can I assume nSigmaPion does not need to be recalibrated? probably - 4 days
% 2006 trigger bias includes the minbias Monte Carlo reweighting hackery - 2 days
% but not just the reweighting hackery, there's also an uncertainty in the size of the jet pT shift - 1 day. And why don't I include pion pt shifts in that calculation? Is it because I choose bin widths to match the pion pT resolution?
% Results - 1 day
% Conclusions - 1.5 days
% Cleanup - 2 days