Tau primary dataset in AOD format from RunB of 2011 (/Tau/Run2011B-12Oct2013-v1/AOD)
/Tau/Run2011B-12Oct2013-v1/AOD, CMS collaboration
Cite as: CMS collaboration (2020). Tau primary dataset in AOD format from RunB of 2011 (/Tau/Run2011B-12Oct2013-v1/AOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.CJYU.OMF5
Dataset Collision CMS 7TeV pp CERN-LHC
Description
Tau primary dataset in AOD format from RunB of 2011. Run period from run number 175833 to 180252.
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
Dataset characteristics
11503040 events. 626 files. 2.2 TiB in total.System details
FT_53_LV5_AN1CMSSW_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?
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 (identical to 2011 RunA):
Step: RECO
Release: CMSSW_5_3_7_patch5
Global tag: FT_R_53_V18::All
Configuration file for RECO step reco_2011_Tau
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_DoubleIsoPFTau20_Trk5
HLT_DoubleIsoPFTau25_Trk5_eta2p1
HLT_DoubleIsoPFTau35_Trk5_eta2p1
HLT_DoubleIsoPFTau40_Trk5_eta2p1
HLT_DoubleIsoPFTau45_Trk5_eta2p1
HLT_DoubleIsoPFTau55_Trk5_eta2p1
HLT_IsoPFTau35_Trk20
HLT_IsoPFTau35_Trk20_MET45
HLT_IsoPFTau35_Trk20_MET60
HLT_IsoPFTau35_Trk20_MET70
HLT_IsoPFTau40_IsoPFTau30_Trk5_eta2p1
HLT_IsoPFTau45_Trk20_MET60
HLT_MediumIsoPFTau35_Trk20
HLT_MediumIsoPFTau35_Trk20_MET60
HLT_MediumIsoPFTau35_Trk20_MET70
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 Virtual Machine. See the instructions for setting up the Virtual Machine and getting started in
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.
