/MET/Run2015D-16Dec2015-v1/AOD, CMS collaboration
Cite as: CMS collaboration (2021). MET primary dataset in AOD format from RunD of 2015 (/MET/Run2015D-16Dec2015-v1/AOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.DAFA.UG8L
Dataset Collision CMS 13TeV pp CERN-LHC
MET primary dataset in AOD 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:
docker.io/cmsopendata/cmssw_7_6_7-slc6_amd64_gcc493:latest
gitlab-registry.cern.ch/cms-cloud/cmssw-docker-opendata/cmssw_7_6_7-slc6_amd64_gcc493:latest
Events stored in this primary dataset were selected because of the presence of high missing transverse energy.
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_7_6_3
Global tag: 76X_dataRun2_v15
Configuration file for RECO step reco_2015D_MET
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_CaloMHTNoPU90_PFMET90_PFMHT90_IDTight_BTagCSV0p72
HLT_CaloMHTNoPU90_PFMET90_PFMHT90_IDTight
HLT_MET200_JetIdCleaned
HLT_MET200
HLT_MET250
HLT_MET300
HLT_MET60_IsoTrk35_Loose
HLT_MET75_IsoTrk50
HLT_MET90_IsoTrk50
HLT_MonoCentralPFJet80_PFMETNoMu120_JetIdCleaned_PFMHTNoMu120_IDTight
HLT_MonoCentralPFJet80_PFMETNoMu120_PFMHTNoMu120_IDTight
HLT_MonoCentralPFJet80_PFMETNoMu90_JetIdCleaned_PFMHTNoMu90_IDTight
HLT_MonoCentralPFJet80_PFMETNoMu90_PFMHTNoMu90_IDTight
HLT_Mu14er_PFMET100_JetIdCleaned
HLT_Mu14er_PFMET100
HLT_Mu3er_PFHT140_PFMET125_JetIdCleaned
HLT_Mu3er_PFHT140_PFMET125
HLT_Mu6_PFHT200_PFMET100_JetIdCleaned
HLT_Mu6_PFHT200_PFMET100
HLT_Mu6_PFHT200_PFMET80_BTagCSV0p72
HLT_Mu6_PFHT200_PFMET80_JetIdCleaned_BTagCSV0p72
HLT_PFMET100_PFMHT100_IDTight
HLT_PFMET110_PFMHT110_IDTight
HLT_PFMET120_BTagCSV0p72
HLT_PFMET120_JetIdCleaned_BTagCSV0p72
HLT_PFMET120_JetIdCleaned_Mu5
HLT_PFMET120_Mu5
HLT_PFMET120_PFMHT120_IDTight
HLT_PFMET170_HBHECleaned
HLT_PFMET170_JetIdCleaned
HLT_PFMET170_NoiseCleaned
HLT_PFMET170
HLT_PFMET300_JetIdCleaned
HLT_PFMET300
HLT_PFMET400_JetIdCleaned
HLT_PFMET400
HLT_PFMET90_PFMHT90_IDTight
HLT_PFMETNoMu120_JetIdCleaned_PFMHTNoMu120_IDTight
HLT_PFMETNoMu120_PFMHTNoMu120_IDTight
HLT_PFMETNoMu90_JetIdCleaned_PFMHTNoMu90_IDTight
HLT_PFMETNoMu90_PFMHTNoMu90_IDTight
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
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
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.