/MET/Run2011A-12Oct2013-v1/AOD, CMS collaboration
Cite as: CMS collaboration (2016). MET primary dataset in AOD format from RunA of 2011 (/MET/Run2011A-12Oct2013-v1/AOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.GTVX.CSFF
Dataset Collision CMS 7TeV pp CERN-LHC
MET 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 or two high-energy jets and high missing transverse energy; or very high missing transverse energy; or at least one high-energy central jet, with or without b-quark-tag requirement, and a high MR razor kinematic variable, defined in terms of the momentum of the two megajes, 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_MET
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_CentralJet80_MET100
HLT_CentralJet80_MET110
HLT_CentralJet80_MET160
HLT_CentralJet80_MET65
HLT_CentralJet80_MET80
HLT_CentralJet80_MET80HF
HLT_CentralJet80_MET95
HLT_DiCentralJet20_BTagIP_MET65
HLT_DiCentralJet20_MET100_HBHENoiseFiltered
HLT_DiCentralJet20_MET80
HLT_DiCentralPFJet30_PFMHT80
HLT_DiCentralPFJet50_PFMHT80
HLT_DiJet60_MET45
HLT_IsoMu15_L1ETM20
HLT_L2Mu60_1Hit_MET40
HLT_L2Mu60_1Hit_MET60
HLT_MET100
HLT_MET100_HBHENoiseFiltered
HLT_MET120
HLT_MET120_HBHENoiseFiltered
HLT_MET200
HLT_MET200_HBHENoiseFiltered
HLT_MET400
HLT_MET65
HLT_MET65_HBHENoiseFiltered
HLT_Mu15_L1ETM20
HLT_PFMHT150
HLT_R014_MR200_CentralJet40_BTagIP
HLT_R014_MR400_CentralJet40_BTagIP
HLT_R014_MR450_CentralJet40_BTagIP
HLT_R020_MR300_CentralJet40_BTagIP
HLT_R020_MR350_CentralJet40_BTagIP
HLT_R030_MR200_CentralJet40_BTagIP
HLT_R030_MR250_CentralJet40_BTagIP
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.