MuOnia primary dataset in NANOAOD format from RunH of 2016 (/MuOnia/Run2016H-UL2016_MiniAODv2_NanoAODv9-v1/NANOAOD)

Name: /MuOnia/Run2016H-UL2016_MiniAODv2_NanoAODv9-v1/NANOAOD
Creator: CMS Collaboration
Published: 2024

/MuOnia/Run2016H-UL2016_MiniAODv2_NanoAODv9-v1/NANOAOD, CMS Collaboration

Cite as: CMS Collaboration (2024). MuOnia primary dataset in NANOAOD format from RunH of 2016 (/MuOnia/Run2016H-UL2016_MiniAODv2_NanoAODv9-v1/NANOAOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.0UTR.A7KQ

Data recorded in 2016 and published in 2024

Dataset Collision CMS 13TeV pp CERN-LHC

Description

MuOnia primary dataset in NANOAOD format from RunH of 2016. Run period from run number 281613 to 284044.

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 MINIAOD dataset:

/MuOnia/Run2016H-UL2016_MiniAODv2-v2/MINIAOD

Dataset characteristics

38094977 events. 22 files. 26.2 GiB in total.

System details

NANOAOD datasets are in the ROOT tree format and their analysis does not require the use of CMSSW or CMS open data environments. They can be analysed with common ROOT and Python tools.

Recommended container image for analyses is available in the following locations (see guide):

gitlab-registry.cern.ch/cms-cloud/root-vnc
gitlab-registry.cern.ch/cms-cloud/python-vnc

Dataset semantics

Variable list

How were these data selected?

Events stored in this primary dataset were selected because of the presence of at least two muons in the event requiring only very low energy and some requirements in the invariant mass for selecting low-mass resonances.

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

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

Step NANO
Release: CMSSW_10_6_26
Global tag: 106X_dataRun2_v35
Configuration file for NANO step ReReco-Run2016H-MuOnia-UL2016_MiniAODv2_NanoAODv9
Output dataset: /MuOnia/Run2016H-UL2016_MiniAODv2_NanoAODv9-v1/NANOAOD

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

Step RECO
Release: CMSSW_10_6_8_patch1
Global tag: 106X_dataRun2_v27
Configuration file for RECO step recoskim_Run2016H_MuOnia
Output dataset: /MuOnia/Run2016H-21Feb2020_UL2016-v1/AOD

HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_Dimuon0_Phi_Barrel
HLT_Dimuon0_Upsilon_Muon
HLT_Dimuon13_Upsilon
HLT_Dimuon8_Upsilon_Barrel
HLT_Mu16_TkMu0_dEta18_Onia
HLT_Mu16_TkMu0_dEta18_Phi
HLT_Mu25_TkMu0_dEta18_Onia
HLT_Mu7p5_L2Mu2_Upsilon
HLT_Mu7p5_Track2_Upsilon
HLT_Mu7p5_Track3p5_Upsilon
HLT_Mu7p5_Track7_Upsilon
HLT_QuadMuon0_Dimuon0_Upsilon

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 XRootD protocol or direct download, and they can be analysed with common ROOT and Python tools. See the instructions for getting started in

Using Docker containers

Getting started with CMS NanoAOD