Instructions base on: CMSSW guide


You need to be on the lpc cluster


After every login type the command below to set the paths

source /cvmfs/

Validate your certificate with the command below

voms-proxy-init -voms cms

If you have any problems look into the Certificate problems? section

cd CMSSW_version/src/DIR

where DIR is going to be your working directory. Later set the enviroment


Certificate problems?

Getting a Certificate

Installing the Certifcate

Storage Space

Storage space is automatically assigned to account in



Basic Structures

  • cmsRun command
    • The CMSSW executable, cmsRun, is configured at run time by the user's job-specific configuration file. This file tells cmsRun
      • which data to us
      • which modules to execute
      • which parameter settings to use for each module
      • what is the order or the executions of modules, called path
      • how the events are filtered within each path, and
      • how the paths are connected to the output files
  • configuration file(card file)
  • Event structure
    • Physically, an event is the result of a single readout of the detector electronics and the signals that will (in general) have been generated by particles, tracks, energy deposits, present in a number of bunch crossings.


Skeleton for compiling

Link to: CMSSW framework, More information about the framework

  • EDProducer: takes input from the event and produces new output which is saved in the event
  • EDAnalyzer: takes input from the event and processes the input without writing information back to the event
  • EDFilter: decides if processing the event can be stopped and continued
  • EventSetup: external service not bound to the event structure which provides information useable by all modules (e.g. Geometry, Magnetic Field, etc.)

Link to: Skeleton Build

  • mkedanlzr : makes a skeleton of a package containing an EDAnalyzer
  • mkedfltr : makes a skeleton of a package containing an EDFilter
  • mkedprod : makes a skeleton of a package containing an EDProducer
  • mkesprod : makes a skeleton of a package containing an ESProducer
  • mkrecord : makes a complete implementation of a Record used by the EventSetup
  • mkdatapkg : makes a skeleton of a package containing an DataPkg
  • mkedlpr : makes a skeleton of a package containing an EDLooper
  • mkskel : makes a skeleton of a package containing a generic C++ code
  • mktsel : makes a skeleton of a package containing an TSelector

Executing the code and using configuration files

Introduction to CMS Configuration Files

All CMS code is run by passing a config file ( to the CMSSW executable, cmsRun.

cmsRun <Configuration File> 

for example:

cmsRun MyConfig

Locating Data Samples


DAS guide

-- JosephYadielCorderoMercado - 2020-08-14

Edit | Attach | Watch | Print version | History: r6 < r5 < r4 < r3 < r2 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r6 - 2018-09-06 - JosephYadielCorderoMercado
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback