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

MinBias0Tesla1 primary dataset in RECO format from the 7 TeV proton-proton run of 2011 (/MinBias0Tesla1/Run2011A-PromptReco-v5/RECO)

/MinBias0Tesla1/Run2011A-PromptReco-v5/RECO, CMS collaboration

Cite as: CMS collaboration (2020). MinBias0Tesla1 primary dataset in RECO format from the 7 TeV proton-proton run of 2011 (/MinBias0Tesla1/Run2011A-PromptReco-v5/RECO). CERN Open Data Portal. DOI:10.7483/OPENDATA.6CN1.UHG5

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


Description

MinBias0Tesla1 primary dataset from the 7 TeV proton-proton run of 2011. These proton-proton data are at the same centre-of-mass energy and have a similar trigger menu to those in Pb-Pb collisions.

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

4720995 events. 143 files. 866.4 GiB in total.

System details

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

How were these data selected?

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_L1SingleJet128_part1
HLT_L1SingleJet36_part1
HLT_L1SingleJet52_part1
HLT_L1SingleJet68_part1
HLT_L1SingleJet92_part1
HLT_ZeroBias_part1

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:

CMS data quality monitoring: Systems and experiences

The CMS Data Quality Monitoring software experience and future improvements

The CMS data quality monitoring software: experience and future prospects

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 with CMS heavy-ion data data in

Running CMS analysis code using Docker

How to install the CMS Virtual Machine

Usage example for CMS 2011 heavy-ion 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.6
CERN