Charmonium primary dataset in AOD format from RunD of 2015 (/Charmonium/Run2015D-16Dec2015-v1/AOD)
/Charmonium/Run2015D-16Dec2015-v1/AOD, CMS collaboration
Cite as: CMS collaboration (2021). Charmonium primary dataset in AOD format from RunD of 2015 (/Charmonium/Run2015D-16Dec2015-v1/AOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.IO20.EBUI
Dataset Collision CMS 13TeV CERN-LHC
Description
Charmonium primary dataset in AOD format from RunD of 2015. Run period from run number 256630 to 260627.
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:
Related datasets
The corresponding MINIAOD dataset:Dataset characteristics
38833112 events. 1471 files. 5.6 TB in total.System details
76X_dataRun2_16Dec2015_v0CMSSW_7_6_7
How were these data selected?
Events stored in this primary dataset were selected because of the presence of at least two muons, or a muon and a track with 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 / RECO
This primary AOD dataset was processed from the RAW dataset by the following step:
Step: RECO
Release: CMSSW_7_6_3
Global tag: 76X_dataRun2_v15
Configuration file for RECO step reco_2015D_Charmonium
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_Dimuon0_Jpsi_Muon
HLT_Dimuon0er16_Jpsi_NoOS_NoVertexing
HLT_Dimuon0er16_Jpsi_NoVertexing
HLT_Dimuon10_Jpsi_Barrel
HLT_Dimuon13_PsiPrime
HLT_Dimuon16_Jpsi
HLT_Dimuon20_Jpsi
HLT_Dimuon6_Jpsi_NoVertexing
HLT_Dimuon8_PsiPrime_Barrel
HLT_DoubleMu4_3_Bs
HLT_DoubleMu4_3_Jpsi_Displaced
HLT_DoubleMu4_JpsiTrk_Displaced
HLT_DoubleMu4_PsiPrimeTrk_Displaced
HLT_Mu7p5_L2Mu2_Jpsi
HLT_Mu7p5_Track2_Jpsi
HLT_Mu7p5_Track3p5_Jpsi
HLT_Mu7p5_Track7_Jpsi
HLT_QuadMuon0_Dimuon0_Jpsi
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
File Indexes
{{$ctrlTbl.files = $ctrl.index_files.files; ""}}
{{$ctrlTbl.totalItems = $ctrl.index_files.total; ""}}
Filename
Size
Filename
Size
Files
{{$ctrlTbl.files = $ctrl.files.files; ""}}
{{$ctrlTbl.totalItems = $ctrl.files.total; ""}}
Filename
Size
Filename
Size
Disclaimer
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.
