/TauPlusX/Run2011A-12Oct2013-v1/AOD, CMS collaboration
Cite as: CMS collaboration (2016). TauPlusX primary dataset in AOD format from RunA of 2011 (/TauPlusX/Run2011A-12Oct2013-v1/AOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.9SYW.PU3F
Dataset Collision CMS 7TeV pp CERN-LHC
TauPlusX primary dataset in AOD format from RunA of 2011. Run period from run number 160404 to 173692.
The list of validated runs, which must be applied to all analyses, can be found in
CMS list of validated runs Cert_160404-180252_7TeV_ReRecoNov08_Collisions11_JSON.txt
docker.io/cmsopendata/cmssw_5_3_32-slc6_amd64_gcc472:latest
gitlab-registry.cern.ch/cms-cloud/cmssw-docker-opendata/cmssw_5_3_32-slc6_amd64_gcc472:latest
Events stored in this primary dataset were selected because of the presence of at least one isolated tau and one isolated electron or muon, or two isolated taus and high missing transverse momentum from jets or a high scalar sum of the jet transverse momenta (HT) in the event.
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_12_patch1
Global tag: FT_R_53_LV5::All
Configuration file for RECO step reco_2011_TauPlusX
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_Ele15_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT
HLT_Ele15_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_LooseIsoPFTau15
HLT_Ele15_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_LooseIsoPFTau20
HLT_Ele15_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_TightIsoPFTau20
HLT_Ele15_CaloIdVT_TrkIdT_LooseIsoPFTau15
HLT_Ele15_CaloIdVT_TrkIdT_LooseIsoPFTau20
HLT_Ele15_CaloIdVT_TrkIdT_TightIsoPFTau20
HLT_Ele18_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_LooseIsoPFTau20
HLT_Ele18_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_MediumIsoPFTau20
HLT_Ele18_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_TightIsoPFTau20
HLT_Ele18_CaloIdVT_TrkIdT_MediumIsoPFTau20
HLT_Ele20_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_MediumIsoPFTau20
HLT_Ele25_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_MediumIsoPFTau25
HLT_HT200_DoubleLooseIsoPFTau10_Trk3_PFMHT35
HLT_HT250_DoubleIsoPFTau10_Trk3_PFMHT35
HLT_HT250_DoubleLooseIsoPFTau10_Trk3_PFMHT35
HLT_HT300_DoubleIsoPFTau10_Trk3_PFMHT40
HLT_HT350_DoubleIsoPFTau10_Trk3_PFMHT45
HLT_HT400_DoubleIsoPFTau10_Trk3_PFMHT50
HLT_IsoMu12_LooseIsoPFTau10
HLT_IsoMu15_LooseIsoPFTau15
HLT_IsoMu15_LooseIsoPFTau20
HLT_IsoMu15_TightIsoPFTau20
HLT_IsoMu15_eta2p1_LooseIsoPFTau20
HLT_IsoMu15_eta2p1_MediumIsoPFTau20
HLT_IsoMu15_eta2p1_TightIsoPFTau20
HLT_Mu15_LooseIsoPFTau15
HLT_Mu15_LooseIsoPFTau20
HLT_QuadJet50_IsoPFTau50
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
You can access these data through the CMS Virtual Machine. See the instructions for setting up the Virtual Machine and getting started in
These open data are released under the Creative Commons Zero v1.0 Universal license.
Neither the experiment(s) ( CMS ) nor CERN endorse any works, scientific or otherwise, produced using these data.
This release has a unique DOI that you are requested to cite in any applications or publications.