TauParked primary dataset in AOD format from Run of 2012 (/TauParked/Run2012C-22Jan2013-v1/AOD)
/TauParked/Run2012C-22Jan2013-v1/AOD, CMS collaboration
Cite as: CMS collaboration (2017). TauParked primary dataset in AOD format from Run of 2012 (/TauParked/Run2012C-22Jan2013-v1/AOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.DFKT.NEM6
Dataset Collision CMS 8TeV CERN-LHC
Description
TauParked primary dataset in AOD format from RunC of 2012. Run period from run number 198022 to 203742.
This dataset contains all runs from 2012 RunC. 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
58371814 events. 4411 files. 16.5 TB in total.System details
FT53_V21A_AN6CMSSW_5_3_32
How were these data selected?
Events stored in this primary dataset were selected because of the presence of more than one isolated tau (with maybe an energetic jet), or at least one isolated tau and high missing transverse energy 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_7_patch5
Global tag: FT_R_53_V18::All
Configuration file for RECO step reco_2012C_TauParked
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_DoubleIsoL2Tau30_eta2p1
HLT_DoubleMediumIsoPFTau30_Trk1_eta2p1
HLT_DoubleMediumIsoPFTau30_Trk1_eta2p1_Jet30
HLT_DoubleMediumIsoPFTau30_Trk1_eta2p1_Reg
HLT_DoubleMediumIsoPFTau30_Trk1_eta2p1_Reg_Jet30
HLT_DoubleMediumIsoPFTau30_Trk5_eta2p1
HLT_DoubleMediumIsoPFTau30_Trk5_eta2p1_Jet30
HLT_DoubleMediumIsoPFTau35_Trk1_eta2p1
HLT_DoubleMediumIsoPFTau35_Trk1_eta2p1_Prong1
HLT_DoubleMediumIsoPFTau35_Trk1_eta2p1_Prong1_Reg
HLT_DoubleMediumIsoPFTau35_Trk1_eta2p1_Reg
HLT_DoubleMediumIsoPFTau35_Trk5_eta2p1
HLT_DoubleMediumIsoPFTau35_Trk5_eta2p1_Prong1
HLT_LooseIsoPFTau35_Trk20_Prong1
HLT_LooseIsoPFTau35_Trk20_Prong1_MET70
HLT_LooseIsoPFTau35_Trk20_Prong1_MET75
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
File Indexes
{{$ctrlTbl.files = $ctrl.index_files.files; ""}}
{{$ctrlTbl.totalItems = $ctrl.index_files.total; ""}}
Filename
Size
Filename
Size
Files
{{$ctrlTbl.files = $ctrl.files.files; ""}}
{{$ctrlTbl.totalItems = $ctrl.files.total; ""}}
Filename
Size
Filename
Size
Disclaimer
The open data are released under the Creative Commons CC0 waiver. Neither 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.
