Tau primary dataset in MINIAOD format from RunD of 2015 (/Tau/Run2015D-16Dec2015-v1/MINIAOD)
/Tau/Run2015D-16Dec2015-v1/MINIAOD, CMS collaboration
Cite as: CMS collaboration (2021). Tau primary dataset in MINIAOD format from RunD of 2015 (/Tau/Run2015D-16Dec2015-v1/MINIAOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.670P.7U69
Dataset Collision CMS 13TeV pp CERN-LHC
Description
Tau primary dataset in MINIAOD format from RunD of 2015. Run period from run number 256630 to 260627.
The list of validated runs, which must be applied to all analyses, either with the full validation or for an analysis requiring only muons, can be found in:
Related datasets
The corresponding AOD dataset:Dataset characteristics
16345128 events. 354 files. 293.6 GiB in total.System details
76X_dataRun2_16Dec2015_v0CMSSW_7_6_7
Recommended container image for analyses is available in the following locations (see guide):
docker.io/cmsopendata/cmssw_7_6_7-slc6_amd64_gcc493:latestgitlab-registry.cern.ch/cms-cloud/cmssw-docker-opendata/cmssw_7_6_7-slc6_amd64_gcc493:latest
How were these data selected?
Events stored in this primary dataset were selected because of the presence of at least one isolated tau, or one isolated tau and high missing transverse momentum.
Data taking / HLT
The collision data were assigned to different RAW datasets using the following HLT configuration.
Data processing / RECO
This primary MINIAOD dataset was processed from the RAW dataset by the following step:
Step: RECO
Release: CMSSW_7_6_3
Global tag: 76X_dataRun2_v15
Configuration file for RECO step reco_2015D_Tau
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_DoubleMediumIsoPFTau35_Trk1_eta2p1_Reg
HLT_DoubleMediumIsoPFTau40_Trk1_eta2p1_Reg
HLT_LooseIsoPFTau50_Trk30_eta2p1_MET120_JetIdCleaned
HLT_LooseIsoPFTau50_Trk30_eta2p1_MET120
HLT_LooseIsoPFTau50_Trk30_eta2p1_MET80_JetIdCleaned
HLT_LooseIsoPFTau50_Trk30_eta2p1_MET80
HLT_LooseIsoPFTau50_Trk30_eta2p1
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:
The Data Quality Monitoring Software for the CMS experiment at the LHC: past, present and future
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.
