• Help
    Discussion forum
    Search tips
  • About
    CERN Open Data
    ALICE
    ATLAS
    CMS
    DELPHI
    LHCb
    OPERA
    TOTEM
    Glossary

ZeroBias4 primary dataset in RECO format from RunA of 2013 (/ZeroBias4/Run2013A-PromptReco-v1/RECO)

/ZeroBias4/Run2013A-PromptReco-v1/RECO, CMS collaboration

Cite as: CMS collaboration (2023). ZeroBias4 primary dataset in RECO format from RunA of 2013 (/ZeroBias4/Run2013A-PromptReco-v1/RECO). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.Q7TU.I2RM

Dataset Collision Heavy-ion physics CMS 2.76TeV pp CERN-LHC


Description

ZeroBias4 primary dataset in RECO format from RunA of 2013. Run period from run number 211739 to 211831.

These proton-proton data were taken at the same centre-of-mass energy and have a similar trigger menu to Pb-Pb collision data from 2010/2011.

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

Dataset characteristics

4455795 events. 104 files. 197.1 GiB in total.

System details

GR_P_V43D::All
CMSSW_5_3_20
Recommended container image for analyses is available in the following locations (see guide):
  • docker.io/cmsopendata/cmssw_5_3_20-slc6_amd64_gcc472:latest
  • gitlab-registry.cern.ch/cms-cloud/cmssw-docker-opendata/cmssw_5_3_20-slc6_amd64_gcc472:latest

How were these data selected?

Events stored in this primary dataset are an unbiased sample of all events. They are directed in several primary datasets for data processing purposes.

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

HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_ZeroBias_part3
HLT_ZeroBias_part4

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 2013 and 2015 Heavy-Ion Open Data


      

Files and indexes

Disclaimer

These open data are released under the Creative Commons Zero v1.0 Universal license.

Logo CC0-1.0

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.

ALICE experiment
ATLAS experiment
CMS experiment
DELPHI experiment
LHCb experiment
OPERA experiment
PHENIX experiment
TOTEM experiment
© CERN, 2014–2025 ·
Terms of Use ·
Privacy Policy ·
Help ·
GitHub ·
Twitter ·
Email
Powered by Invenio
Open Data Portal v0.4.8
CERN