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

Jet primary dataset sample in RAW format from RunB of 2010 (from /Jet/Run2010B-v1/RAW)

/Jet/Run2010B-v1/RAW, CMS collaboration

Cite as: CMS collaboration (2019). Jet primary dataset sample in RAW format from RunB of 2010 (from /Jet/Run2010B-v1/RAW). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.1EHR.R5N3

Dataset Collision CMS 7TeV pp CERN-LHC


Description

A sample from Jet primary dataset in RAW format from RunB of 2010. Run range [146807, 147043].

This dataset contains selected runs from 2010 RunB. The list of validated lumi sections, which must be applied to all analyses on events reconstructed from these data, can be found in

CMS list of validated runs Cert_136033-149442_7TeV_Apr21ReReco_Collisions10_JSON_v2.txt

Dataset characteristics

2415753 events. 106 files. 353.4 GiB in total.

System details

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

How were these data selected?

Events stored in this primary dataset were selected because of presence of at least one high-energy jet in the event.


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_DiJetAve100U
HLT_DiJetAve140U
HLT_DiJetAve15U
HLT_DiJetAve30U
HLT_DiJetAve50U
HLT_DiJetAve70U
HLT_HT120U
HLT_HT140U
HLT_Jet100U
HLT_Jet140U
HLT_Jet15U
HLT_Jet15U_HcalNoiseFiltered
HLT_Jet180U
HLT_Jet30U
HLT_Jet50U
HLT_Jet70U
HLT_QuadJet20U
HLT_QuadJet25U

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?

These data are in RAW format and not directly usable in analysis. The reconstructed data reprocessed from these RAW data are included in the data of this record. The reconstruction step can be repeated with the configuration file attached to this record and the resulting AOD has been confirmed to be identical with the original one with comparison code available in Validation code to plot basic physics objects from AOD

Configuration file for reconstruction


      

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