ViewVC Help
View File | Revision Log | Show Annotations | Root Listing
root/cvsroot/UserCode/benhoob/cmsnotes/ZMet2012/datasets.tex
(Generate patch)

Comparing UserCode/benhoob/cmsnotes/ZMet2012/datasets.tex (file contents):
Revision 1.2 by benhoob, Mon Jun 25 11:45:56 2012 UTC vs.
Revision 1.6 by benhoob, Wed Sep 12 08:24:02 2012 UTC

# Line 7 | Line 7 | In this section we list the datasets, tr
7   events, we use dilepton triggers in the DoubleElectron, DoubleMu, and MuEG datasets.
8   An event in the ee final state is required to pass the dielectron trigger, a
9   $\mu\mu$ event is required to pass the dimuon trigger, while an e$\mu$ event is required to pass at least one
10 < of the two $e-\mu$ cross triggers. Our signal region consists of same-flavor (SF) ee and $\mu\mu$ events, while
11 < opposite-flavor (OF) $e\mu$ events are retained in a control sample used to estimate the
12 < FS contribution as described. A sample of \gjets\ events, used as a control sample to estimate the \zjets\
10 > of the two $e-\mu$ cross triggers. The efficiencies of the ee, $\mu\mu$ and e$\mu$ triggers with respect to the
11 > offline selection have been measured as $0.95\pm0.03$, $0.88\pm0.03$, and $0.92\pm0.03$, respectively~\cite{ref:SSAN}.  
12 > {\bf These trigger efficiencies were measured with the first 5.1 fb$^{-1}$ and will be updated with the full data sample. Preliminary measurements of the trigger efficiency with the full sample show consistent results within $\sim1-2$\%.}
13 > A sample of \gjets\ events, used as a control sample to estimate the \zjets\
14   background, is selected using a set of single photon triggers.
15 < The golden json of June 15th, corresponding to an integrated luminosity of \lumi.
16 <
17 < {\bf UPDATE LIST OF MC SAMPLES}.
15 > The golden json of Aug 31st, corresponding to an integrated luminosity of 9.7 fb$^{-1}$, is used as the starting point.
16 > However, due to a bug in the Run2012C-PromptReco-v1 data samples (corresponding to 0.5 fb$^{-1}$), this portion of the data
17 > is currently excluded but will be added back after its reprocessed. Thus we currently use a sample corresponding to \lumi.
18 > {\bf UPDATE DATASETS, MC SAMPLES, AND JSON, AND ADD CROSS SECTIONS USED FOR MC SAMPLES.}
19  
20   \begin{itemize}
21   \item Datasets
# Line 41 | Line 43 | The golden json of June 15th, correspond
43  
44   \item Good run list
45    \begin{itemize}
46 <    \item \verb=Cert_190456-195947_8TeV_PromptReco_Collisions12_JSON.txt=
46 >    \item \verb=Cert_190456-196531_8TeV_PromptReco_Collisions12_JSON.txt=
47    \end{itemize}
48    
49   \item MC samples
50    \begin{itemize}
51 <  \item {\footnotesize \verb=/DYJetsToLL_TuneD6T_M-50_7TeV-madgraph-tauola/Spring11-PU_S1_START311_V1G1-v1/AODSIM=}
51 >  \item {\footnotesize \verb=/DYJetsToLL_M-50_TuneZ2Star_8TeV-madgraph-tarball/Summer12-PU_S7_START52_V9-v2=}
52 >  \item {\footnotesize \verb=/TTJets_TuneZ2star_8TeV-madgraph-tauola/Summer12-PU_S7_START52_V9-v1=}
53 >  \item {\footnotesize \verb=/WZJetsTo3LNu_TuneZ2_8TeV-madgraph-tauola/Summer12-PU_S7_START52_V9-v2=}
54 >  \item {\footnotesize \verb=/WZJetsTo2L2Q_TuneZ2star_8TeV-madgraph-tauola/Summer12-PU_S7_START52_V9-v1=}
55 >  \item {\footnotesize \verb=/ZZJetsTo2L2Q_TuneZ2star_8TeV-madgraph-tauola/Summer12-PU_S7_START52_V9-v3=}
56 >  \item {\footnotesize \verb=/ZZJetsTo2L2Nu_TuneZ2star_8TeV-madgraph-tauola/Summer12-PU_S7_START52_V9-v3=}
57 >  \item {\footnotesize \verb=/ZZJetsTo4L_TuneZ2star_8TeV-madgraph-tauola/Summer12-PU_S7_START52_V9-v3=}
58 >  \item {\footnotesize \verb=/WWJetsTo2L2Nu_TuneZ2star_8TeV-madgraph-tauola/Summer12-PU_S7_START52_V9-v1=}
59 >  \item {\footnotesize \verb=/T_tW-channel-DR_TuneZ2star_8TeV-powheg-tauola/Summer12-PU_S7_START52_V9-v1=}
60 >  \item {\footnotesize \verb=/Tbar_tW-channel-DR_TuneZ2star_8TeV-powheg-tauola/Summer12-PU_S7_START52_V9-v1=}
61   \end{itemize}
62   \end{itemize}
63  

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines