MET primary dataset in AOD format from Run of 2012 (/MET/Run2012A-22Jan2013-v1/AOD)
/MET/Run2012A-22Jan2013-v1/AOD, CMS collaboration
Cite as: CMS collaboration (2022). MET primary dataset in AOD format from Run of 2012 (/MET/Run2012A-22Jan2013-v1/AOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.IGU3.PCK6
Dataset Collision CMS 8TeV pp CERN-LHC
Description
MET primary dataset in AOD format from RunA of 2012. Run period from run number 190456 to 193621.
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
4934732 events. 338 files. 1.1 TiB in total.System details
FT53_V21A_AN6CMSSW_5_3_32
Recommended container image for analyses is available in the following locations (see guide):
docker.io/cmsopendata/cmssw_5_3_32-slc6_amd64_gcc472:latestgitlab-registry.cern.ch/cms-cloud/cmssw-docker-opendata/cmssw_5_3_32-slc6_amd64_gcc472:latest
How were these data selected?
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.
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_2012A_MET
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_CentralPFJet80_CaloMET50_dPhi1_PFMHT80_HBHENoiseFiltered
HLT_DiCentralJet20_BTagIP_MET65_HBHENoiseFiltered_dPhi1
HLT_DiCentralJet20_CaloMET65_BTagCSV07_PFMHT80
HLT_DiCentralJetSumpT100_dPhi05_DiCentralPFJet60_25_PFMET100_HBHENoiseCleaned
HLT_DiCentralPFJet30_CaloMET50_dPhi1_PFMHT80_HBHENoiseFiltered
HLT_DiCentralPFJet30_PFMET80
HLT_DiCentralPFJet30_PFMET80_BTagCSV07
HLT_DiCentralPFJet30_PFMHT80
HLT_DiCentralPFJet50_PFMET80
HLT_DiCentralPFNoPUJet50_PFMETORPFMETNoMu80
HLT_DiPFJet40_PFMETnoMu65_MJJ600VBF_LeadingJets
HLT_DiPFJet40_PFMETnoMu65_MJJ800VBF_AllJets
HLT_L1ETM100
HLT_L1ETM30
HLT_L1ETM40
HLT_L1ETM70
HLT_MET120
HLT_MET120_HBHENoiseCleaned
HLT_MET200
HLT_MET200_HBHENoiseCleaned
HLT_MET300
HLT_MET300_HBHENoiseCleaned
HLT_MET400
HLT_MET400_HBHENoiseCleaned
HLT_MonoCentralPFJet80_PFMETnoMu105_NHEF0p95
HLT_MonoCentralPFJet80_PFMETnoMu95_NHEF0p95
HLT_PFMET150
HLT_PFMET180
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 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
Files and indexes
Disclaimer
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.
