Muon ID Z to mumu p17 Data Sample
The p17 sample consists of ~200 000 events. About 100k are well reconstructed Z->mumu events.
These are raw data, pick-evented following this event-list.
If handeld properly, the sample is free of bias to
be used for: - tracking efficiency studies,
- muonid efficiency studies,
- isolation efficiency studies,
- trigger studies (at L1, L2, L3).
The event list was obtained as follows:
- wzreco+muo_cert (CVS tag v04-00-07/v04-00-07) selection applied on two TMB samples:
- p17 fixed (but not refixed!) 2MuHighPt skim as was available in January 2006. So this was p17.07.00, p17.07.01 data as described here.
- 2MuHighPt skim from data taken after november 2005, aka p17.09.01 as described here.
- wzreco+muo_cert aim at selecting Z->mumu candidate following tag and probe methods.
The selected events are either:
1. Zmumu events (mu1+track1, mu2+track2). By requiring isolation on mu1+track1, the mu2+track2 system can be used to study isolation efficiency.
2. (mu1+track1, mu2) and dimuon trigger requirement to compute either tracking efficiency or track_trigger efficiency for mu2.
3. (mu1+track1+single muon trigger,track2)
to compute either muonid efficiency or muon trigger efficiency or track trigger efficiency for mu2.
More details are given in wzreco documentation or in muo_cert wiki.
- wzreco+muo_cert selection is actually loosen with respect to the default, using the following wzreco RCP.
Be aware that using looser cuts or looser trigger requirements than what is in the RCP could yield to efficiency biases.