MuonEG primary dataset in MINIAOD format from RunG of 2016 (/MuonEG/Run2016G-UL2016_MiniAODv2-v2/MINIAOD)

Name: /MuonEG/Run2016G-UL2016_MiniAODv2-v2/MINIAOD
Creator: CMS Collaboration
Published: 2024

/MuonEG/Run2016G-UL2016_MiniAODv2-v2/MINIAOD, CMS Collaboration

Cite as: CMS Collaboration (2024). MuonEG primary dataset in MINIAOD format from RunG of 2016 (/MuonEG/Run2016G-UL2016_MiniAODv2-v2/MINIAOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.0VA7.931R

Dataset Collision CMS 13TeV pp CERN-LHC Parent Dataset:

Description

MuonEG primary dataset in MINIAOD format from RunG of 2016. Run period from run number 278820 to 280385.

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:

Validated runs, full validation

Validated runs, muons only

Related datasets

The corresponding NANOAOD dataset:

/MuonEG/Run2016G-UL2016_MiniAODv2_NanoAODv9-v1/NANOAOD

Dataset characteristics

33854612 events. 353 files. 1.1 TiB in total.

System details

Recommended global tag for analysis: 106X_dataRun2_v37
Recommended release for analysis: CMSSW_10_6_30
Recommended container image for analyses is available in the following locations (see guide):

docker.io/cmsopendata/cmssw_10_6_30-slc7_amd64_gcc700:latest
gitlab-registry.cern.ch/cms-cloud/cmssw-docker-opendata/cmssw_10_6_30-slc7_amd64_gcc700:latest

How were these data selected?

Events stored in this primary dataset were selected because of the presence of one energetic muon and electron or photon.

Data taking / HLT
The collision data were assigned to different RAW datasets using the following HLT configuration.

Data processing
This MINIAOD dataset was processed from the RAW dataset by the following steps:

Step PAT
Release: CMSSW_10_6_25
Global tag: 106X_dataRun2_v35
Configuration file for PAT step ReReco-Run2016G-MuonEG-UL2016_MiniAODv2
Output dataset: /MuonEG/Run2016G-UL2016_MiniAODv2-v2/MINIAOD

Step RECO
Release: CMSSW_10_6_8_patch1
Global tag: 106X_dataRun2_v27
Configuration file for RECO step recoskim_Run2016G_MuonEG
Output dataset: /MuonEG/Run2016G-21Feb2020_UL2016-v1/AOD

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

How to install the CMS Virtual Machine

Getting started with CMS open data

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.