TauPlusX primary dataset in AOD format from Run of 2012 (/TauPlusX/Run2012B-22Jan2013-v1/AOD)
/TauPlusX/Run2012B-22Jan2013-v1/AOD, CMS collaboration
Cite as: CMS collaboration (2017). TauPlusX primary dataset in AOD format from Run of 2012 (/TauPlusX/Run2012B-22Jan2013-v1/AOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.RL5Z.NNUG
Dataset Collision CMS 8TeV pp CERN-LHC
Description
TauPlusX primary dataset in AOD format from RunB of 2012. Run period from run number 193833 to 196531.
The list of validated runs, which must be applied to all analyses, can be found in
CMS list of validated runs Cert_190456-208686_8TeV_22Jan2013ReReco_Collisions12_JSON.txt
Dataset characteristics
39411579 events. 3006 files. 10.1 TiB in total.System details
FT53_V21A_AN6CMSSW_5_3_32
Recommended container image for analyses is available in the following locations (see guide):
docker.io/cmsopendata/cmssw_5_3_32-slc6_amd64_gcc472:latestgitlab-registry.cern.ch/cms-cloud/cmssw-docker-opendata/cmssw_5_3_32-slc6_amd64_gcc472:latest
How were these data selected?
Events stored in this primary dataset were selected because of the presence of at least one isolated tau and one isolated electron or muon.
Data taking / HLT
The collision data were assigned to different RAW datasets using the following HLT configuration.
Data processing / RECO
This primary AOD dataset was processed from the RAW dataset by the following step:
Step: RECO
Release: CMSSW_5_3_7_patch5
Global tag: FT_R_53_V18::All
Configuration file for RECO step reco_2012B_TauPlusX
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_Ele13_eta2p1_WP90NoIso_LooseIsoPFTau20_L1ETM36
HLT_Ele13_eta2p1_WP90Rho_LooseIsoPFTau20
HLT_Ele13_eta2p1_WP90Rho_LooseIsoPFTau20_L1ETM36
HLT_Ele20_CaloIdVT_CaloIsoRhoT_TrkIdT_TrkIsoT
HLT_Ele20_CaloIdVT_CaloIsoRhoT_TrkIdT_TrkIsoT_LooseIsoPFTau20
HLT_Ele20_CaloIdVT_CaloIsoRhoT_TrkIdT_TrkIsoT_LooseIsoPFTau20L1Jet
HLT_Ele20_CaloIdVT_CaloIsoRhoT_TrkIdT_TrkIsoT_LooseIsoPFTau22L1Jet
HLT_Ele20_CaloIdVT_TrkIdT_LooseIsoPFTau20
HLT_Ele22_CaloIdVT_CaloIsoRhoT_TrkIdT_TrkIsoT_LooseIsoPFTau20
HLT_Ele22_eta2p1_WP90NoIso_LooseIsoPFTau20
HLT_Ele22_eta2p1_WP90Rho_LooseIsoPFTau20
HLT_IsoMu15_eta2p1_L1ETM20
HLT_IsoMu15_eta2p1_LooseIsoPFTau35_Trk20_Prong1_L1ETM20
HLT_IsoMu17_eta2p1_LooseIsoPFTau20
HLT_IsoMu18_eta2p1_LooseIsoPFTau20
HLT_IsoMu18_eta2p1_MediumIsoPFTau25_Trk1_eta2p1
HLT_IsoMu18_eta2p1_MediumIsoPFTau25_Trk1_eta2p1_Reg
HLT_IsoMu18_eta2p1_MediumIsoPFTau25_Trk5_eta2p1
HLT_IsoMu20_eta2p1_LooseIsoPFTau20
HLT_IsoMu8_eta2p1_LooseIsoPFTau20
HLT_IsoMu8_eta2p1_LooseIsoPFTau20_L1ETM26
HLT_Mu15_eta2p1_L1ETM20
HLT_Mu17_eta2p1_LooseIsoPFTau20
HLT_Mu18_eta2p1_LooseIsoPFTau20
HLT_Mu8_eta2p1_LooseIsoPFTau20_L1ETM26
How were these data validated?
During data taking all the runs recorded by CMS are certified as good for physics analysis if all subdetectors, trigger, lumi and physics objects (tracking, electron, muon, photon, jet and MET) show the expected performance. Certification is based first on the offline shifters evaluation and later on the feedback provided by detector and Physics Object Group experts. Based on the above information, which is stored in a specific database called Run Registry, the Data Quality Monitoring group verifies the consistency of the certification and prepares a json file of certified runs to be used for physics analysis. For each reprocessing of the raw data, the above mentioned steps are repeated. For more information see:
CMS data quality monitoring: Systems and experiences
The CMS Data Quality Monitoring software experience and future improvements
The CMS data quality monitoring software: experience and future prospects
How can you use these data?
You can access these data through the CMS Open Data container or the CMS Virtual Machine. See the instructions for setting up one of the two alternative environments and getting started in
Running CMS analysis code using Docker
Disclaimer
The open data are released under the Creative Commons CC0 waiver. Neither the experiment(s) ( CMS ) nor CERN endorse any works, scientific or otherwise, produced using these data. All releases will have a unique DOI that you are requested to cite in any applications or publications.
