/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
MET primary dataset in AOD format from RunA of 2011. Run period from run number 160404 to 173692.
This dataset contains all runs from 2011 RunA. The list of validated runs, which must be applied to all analyses, can be found in
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:
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:
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 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.