This file was generated by Timo Saala and Matthias Schott


A GENERAL INFORMATION

1. Title of the dataset: pandas DataFrames of the DYToMuMu_M-20_CT10_TuneZ2star_v2_8TeV process

2. Brief description of the research project and its aims: 
Within this project CMS Open Data from the 2012 LHC run is taken (both simulated data and real collisions) and transformed to pandas
DataFrames. Initially, the data is stored on the CERN Open Data Portal in the form of ROOT files, a file format commonly used in the 
context of high energy physics. In other scientific spheres, ROOT is very rarely applied or known, hence the benefit of transforming them
to a commonly used data format - especially in the context of machine learning - namely pandas DataFrames.
The aim of this project is therefore to make publicly available data from CERN more approachable to interested people and researchers 
that do not posess prior knowledge on ROOT files.
Additionally, we provide a paper (https://arxiv.org/abs/2501.06896) in which we explain the physics between the variables encountered in the 
provided data, as well as some examplary analyses based on this data (both physics-based analyses, as well as deep learning based analyses).

3. Author Information
	A. Investigator Contact Information
		Name: Timo Saala
		Institution: University of Bonn
		Address: Nußallee 12, 53115 Bonn
		Email: tsaala@uni-bonn.de

	B. Project Supervisor (Principal Investigator) Contact Information
		Name: Matthias Schott
		Institution: University of Bonn
		Address: Nußallee 12, 53115 Bonn
		Email: mschott@uni-bonn.de

	C. In case of questions related to this dataset, please contact:
		Name: Timo Saala
		Institution: University of Bonn
		Address: Nußallee 12, 53115 Bonn
		Email: tsaala@uni-bonn.de

4. Date of data collection: 
2012 (OpenData), 2024 (pandas DataFrame)

5. Information about funding sources that supported the collection of the data: 
The data was collected/generated initially by the CMS Collaboration.

6. Language of the dataset: 
English

7. Geographic location of data collection: 
CERN



B DATA & FILE OVERVIEW

1. File List: 
DYToMuMu_M-20_CT10_TuneZ2star_v2_8TeV_0.feather,
DYToMuMu_M-20_CT10_TuneZ2star_v2_8TeV_1.feather,
DYToMuMu_M-20_CT10_TuneZ2star_v2_8TeV_2.feather,
DYToMuMu_M-20_CT10_TuneZ2star_v2_8TeV_3.feather,
DYToMuMu_M-20_CT10_TuneZ2star_v2_8TeV_4.feather,
DYToMuMu_M-20_CT10_TuneZ2star_v2_8TeV_5.feather,
DYToMuMu_M-20_CT10_TuneZ2star_v2_8TeV_6.feather,
DYToMuMu_M-20_CT10_TuneZ2star_v2_8TeV_7.feather,
DYToMuMu_M-20_CT10_TuneZ2star_v2_8TeV_8.feather,
DYToMuMu_M-20_CT10_TuneZ2star_v2_8TeV_9.feather


2. Are there multiple versions of the dataset? no
	2.1 If yes, name of file(s) that was updated: 
		i. Why was the file updated? 
		ii. When was the file updated? 

3. Relationship between files: 
All files are of the same origin process (DYToMuMu_M-20_CT10_TuneZ2star_v2_8TeV) generated by the CMS collaboration

4. Additional related data collected that was not included in the current data package: 



C SHARING/ACCESS INFORMATION

1. Was data derived from another source? yes: 
From the CMS Open Data initiative (http://doi.org/10.7483/OPENDATA.CMS.UQL1.0C31)

2. Licenses/restrictions placed on the data: 
CC-BY

3. Links to publications that cite or use the data: 
https://arxiv.org/abs/2501.06896

4. Links to other publicly accessible locations of the data: 


5. Links/relationships to ancillary datasets: 



D METHODOLOGICAL INFORMATION

1. Description of methods used for collection/generation of data: 
The data was collected by the CMS collaboration with the CMS detector at the Large Hadron Collider. 
Simulated data-sets have been generated by the CMS collaboration. 
This particular data-set represents simulated/recorded particle collisions in a Drell-Yan to Muon Muon decay.

2. Methods for processing the data: 
The generated processes are stored on the CMS Open Data portal (CERN Open Data) as ROOT files. We then take these initial ROOT files, filter
them such that we are left with a subset of 121 variables we deem relevant, and transform the filtered subset of data to pandas DataFrames.
The pipeline and a guide to use it in order to transform CMS Open Data (from the 2012 run) can be found here: https://github.com/TSaala/OpenDataToDataFrame

3. Instrument- and/or software-specific information needed to interpret the data: 
python, pandas
A quick example of reading and filtering the data using python and pandas is provided in the accompanying Example.py file.

4. People involved in sample collection, processing, analysis and/or submission: 
CMS Collaboration, Timo Saala, Matthias Schott

5. Describe any quality-assurance procedures performed on the data: 
Quality-assurance was provided by the CMS Collaboration.
6. Standards and calibration information <when relevant>: 

7. Environmental/experimental conditions <when relevant>: 



E DATA-SPECIFIC INFORMATION FOR: DYToMuMu_M-20_CT10_TuneZ2star_v2_8TeV

1. Variable list including full names and definitions (please spell out abbreviated words) of column headings for tabular data: 
A full description of the variables including their definitions can be found in the accompanying paper.

nEvent, runNum, lumisection, evtNum;
nMuon, vecMuon_PT, vecMuon_Eta, vecMuon_Phi, vecMuon_PTErr, vecMuon_Q, vecMuon_StaPt, vecMuon_StaEta, vecMuon_StaPhi, vecMuon_TrkIso03, vecMuon_EcalIso03, vecMuon_HcalIso03;
nVertex, vecVertex_nTracksfit, vecVertex_ndof, vecVertex_Chi2, vecVertex_X, vecVertex_Y, vecVertex_Z;
nEle, vecEle_PT, vecEle_Eta, vecEle_Phi, vecEle_Q, vecEle_TrkIso03, vecEle_EcalIso03, vecEle_HcalIso03, vecEle_D0, vecEle_Dz;
nTau, vecTau_PT, vecTau_Eta, vecTau_Phi, vecTau_Q, vecTau_RawIso3Hits, vecTau_RawIsoMVA3oldDMwoLT, vecTau_RawIsoMVA3oldDMwLT, vecTau_RawIsoMVA3newDMwoLT, vecTau_RawIsoMVA3newDMwLT;
nPhoton, vecPhoton_PT, vecPhoton_Eta, vecPhoton_Phi, vecPhoton_Hovere, vecPhoton_Sthovere, vecPhoton_HasPixelSeed, vecPhoton_IsConv, vecPhoton_PassElectronVeto;
nMctruth, vecMctruth_PT, vecMctruth_Eta, vecMctruth_Phi, vecMctruth_Id_1, vecMctruth_Id_2, vecMctruth_X_1, vecMctruth_X_2, vecMctruth_PdgId, vecMctruth_Status, vecMctruth_Y, vecMctruth_Mass, vecMctruth_Mothers.first, vecMctruth_Mothers.second;
nJets, vecJet_PT, vecJet_Eta, vecJet_Phi, vecJet_D0, vecJet_Dz, vecJet_nCharged, vecJet_nNeutrals, vecJet_nParticles, vecJet_Beta, vecJet_BetaStar, vecJet_dR2Mean, vecJet_Q, vecJet_Mass, vecJet_Area, vecJet_Energy, vecJet_chEmEnergy, vecJet_neuEmEnergy, vecJet_chHadEnergy, vecJet_neuHadEnergy, vecJet_ID, vecJet_Num, vecJet_mcFlavor, vecJet_GenPT, vecJet_GenEta, vecJet_GenPhi, vecJet_GenMass, vecJet_flavorMatchPT, vecJet_JEC, vecJet_MatchIdx;
nPF, vecPF_PT, vecPF_Eta, vecPF_Phi, vecPF_Mass, vecPF_E, vecPF_Q, vecPF_PfType, vecPF_EcalE, vecPF_HcalE, vecPF_ndof, vecPF_Chi2, vecPF_pvId, vecPF_X, vecPF_Y, vecPF_Z, vecPF_JetNum;
fMET_PT, fMET_Eta, fMET_Phi;
HLT_Mu17_Mu8, HLT_Mu24, HLT_MET120_v, HLT_Ele27, HLT_HT350

2. Units of measurement used:

3. Missing data codes/symbols: 

4. Specialized formats or other abbreviations used: