| 1 |
|
\section{Event Preselection} |
| 2 |
|
\label{sec:eventSel} |
| 3 |
< |
%{\color{red} This needs to be fixed up -- probably many mistakes present.}\\ |
| 4 |
< |
As mentioned in the introduction, the preselection is based on the |
| 5 |
< |
$t\bar{t}$ analysis. We select events with two opposite sign isolated |
| 3 |
> |
The purpose of the preselection is to define a data sample rich |
| 4 |
> |
in $t\bar{t} \to$ dileptons. We compare the kinematical |
| 5 |
> |
properties of this sample with expectations from $t\bar{t}$ |
| 6 |
> |
Monte Carlo. |
| 7 |
> |
|
| 8 |
> |
The preselection is based on the |
| 9 |
> |
$t\bar{t}$ analysis~\cite{ref:top}. |
| 10 |
> |
We select events with two opposite sign isolated |
| 11 |
|
leptons ($ee$, $e\mu$, or $\mu\mu$); one of the leptons must |
| 12 |
|
have $P_T > 20$ GeV, |
| 13 |
< |
the other one must have $P_T > 10$ GeV. In case of events with |
| 13 |
> |
the other one must have $P_T > 10$ GeV. Events consistent with $Z$ are rejected. |
| 14 |
> |
In case of events with |
| 15 |
|
more than two such leptons, we select the pair that maximizes the scalar |
| 16 |
|
sum of lepton $P_T$'s. |
| 17 |
|
There must be two JPT |
| 18 |
|
jets of $P_T > 30$ GeV and $|\eta| < 2.5$; the scalar sum of the |
| 19 |
|
$P_T$ of all such jets must exceed 100 GeV; jets must pass |
| 20 |
< |
{\tt caloJetId} and be separated by $\Delta R >$ 0.4 from the |
| 21 |
< |
two selected leptons. |
| 16 |
< |
%%%TO BE REPLACED |
| 17 |
< |
%{\color{red}The 11 pb iteration only does this for the two selected |
| 18 |
< |
%leptons.} |
| 19 |
< |
% |
| 20 |
> |
{\tt caloJetId} and be separated by $\Delta R >$ 0.4 from any |
| 21 |
> |
lepton passing the selection. |
| 22 |
|
Finally $\met > 50$ GeV (we use tcMet). More details are given in the subsections below. |
| 23 |
|
|
| 24 |
|
\subsection{Event Cleanup} |
| 61 |
|
\item At least one of the hits from the |
| 62 |
|
standalone muon must be used in the global fit. |
| 63 |
|
|
| 64 |
< |
%\item Require tracker $\Delta P_T/P_T < 0.1$. This cut was not in the original top analysis. |
| 65 |
< |
%It is motivated by the observation of |
| 66 |
< |
%poorly measured muons in data with large |
| 67 |
< |
%relative $P_T$ uncertainty, giving significant contributions to the \met. |
| 64 |
> |
\item Require tracker $\Delta P_T/P_T < 0.1$. This cut was not in the original top analysis. |
| 65 |
> |
It is motivated by the observation of |
| 66 |
> |
poorly measured muons in data with large |
| 67 |
> |
relative $P_T$ uncertainty, giving significant contributions to the \met. |
| 68 |
|
%{\color{red} This is not applied to the 11 pb iteration.} |
| 69 |
|
|
| 70 |
|
|
| 80 |
|
|
| 81 |
|
\begin{itemize} |
| 82 |
|
|
| 83 |
< |
\item $P_T > 10$ GeV. (The $t\bar{t}$ analysis uses 20 GeV but for |
| 84 |
< |
completeness we calculate FR down to 10 GeV). |
| 83 |
> |
% \item $P_T > 10$ GeV. (The $t\bar{t}$ analysis uses 20 GeV but for |
| 84 |
> |
% completeness we calculate FR down to 10 GeV). |
| 85 |
|
|
| 86 |
|
\item $|\eta| < 2.5$. |
| 87 |
|
|
| 121 |
|
|
| 122 |
|
We remove $e^+e^-$ and $\mu^+ \mu^-$ events with invariant |
| 123 |
|
mass between 76 and 106 GeV. We also remove events |
| 124 |
< |
with invariant mass $<$ 10 GeV. |
| 124 |
> |
with invariant mass $<$ 10 GeV, since this kinematical region is |
| 125 |
> |
not well reprodced in CMS Monte Carlos. |
| 126 |
> |
|
| 127 |
> |
In addition, we remove $Z \to \mu\mu\gamma$ |
| 128 |
> |
candidates with the $\gamma$ collinear with one of the muons. This is |
| 129 |
> |
done as follows: |
| 130 |
> |
if the ecal energy associated with one of the muons is greater than 6 GeV, |
| 131 |
> |
we add this energy to the momentum of the initial muon, and we recompute |
| 132 |
> |
the $\mu\mu$ mass. If this mass is between 76 and 106 GeV, the event is rejected. |
| 133 |
> |
|
| 134 |
|
|
| 135 |
|
\subsection{Trigger Selection} |
| 136 |
|
\label{sec:trigSel} |
| 137 |
|
|
| 138 |
|
Because most of the triggers implemented in the 2nd half of the |
| 139 |
< |
2010 run were not implemented in the Monte Carlo, no trigger |
| 140 |
< |
selection is applied on Monte Carlo data. As discussed in |
| 139 |
> |
2010 run were not implemented in the Monte Carlo, |
| 140 |
> |
we do not make any requirements on HLT bits in the Monte Carlo. |
| 141 |
> |
Instead, as discussed in |
| 142 |
|
Section~\ref{sec:trgEff}, a trigger efficiency weight is applied |
| 143 |
|
to each event, based on the trigger efficiencies measured on data. |
| 144 |
|
Trigger efficiency weights are very close to 1. |
| 159 |
|
% We currently |
| 160 |
|
% do not require MC events to pass any triggers. |
| 161 |
|
|
| 162 |
+ |
|
| 163 |
+ |
|
| 164 |
+ |
|
| 165 |
+ |
|
| 166 |
+ |
|
| 167 |
+ |
|
| 168 |
+ |
|
| 169 |
+ |
|
| 170 |
|
\begin{itemize} |
| 171 |
|
\item single-muon triggers |
| 172 |
|
\begin{itemize} |
