This page contains an explanation for the available .CFG examples. This are the examples you should refer to if you want to prepare "standard" configurations files ( == no too fancy options).

Files

GenExample.cfg:Example config file for event generation. The options are
- PGunParameters: gun configuration.
- Output file: edit filename to match the wanted output file.
SimExample.cfg:Example config file for Simulation. The options are
- Input file: edit filename to match the wanted intput file.
- Output file: edit filename to match the wanted output file.
- vertex smearing option: see Package Configuration/StandardSequences.
- Conditions: at the moment, the only available is FakeConditions.
RecoExample.cfg: Example config file for Reconstruction. The only options available are
- Input file: edit filenames to match the input file.
- Output file: edit filename to match the wanted output file.
- path: use one of the paths explained in the Reconstruction.cff fragment.
- calibrations: choose the calibration sources.
- Data Tier: choose between FEVT, RECO, AOD, FEVTSIM, RECOSIM, AODSIM.
- Conditions: at the moment, the only available is FakeConditions.
FullChainExample.cfg: Example config file for a full chain processing (from 0 to reconstructed sample). It has the same options as the RecoExample.cfg, plus these simulation related
- vertex smearing option: see Package Configuration/StandardSequences.
- mixing option: see Package Configuration/StandardSequences.
DigiRecoExample.cfg: Example config file to run/re-run Digitization and Reconstruction. The only options available are
- mixing option: see Package Configuration/StandardSequences.
- Input file: edit filenames to match the input file.
- Output file: edit filename to match the wanted output file.
- path: use one of the paths explained in the Reconstruction.cff fragment.
- calibrations: choose the calibration sources.
- Data Tier: choose between FEVT, RECO, AOD, FEVTSIM, RECOSIM, AODSIM.
DigiRecoExample_123.cfg: Example config file to run/re-run Digitization and Reconstruction with 130 on 123 data. The only options available are
- mixing option: see Package Configuration/StandardSequences
- Input file: edit filenames to match the input file
- Output file: edit filename to match the wanted output file
- path: use one of the paths explained in the Reconstruction.cff fragment.
- calibrations: choose the calibration sources.
- Data Tier: choose between FEVT, RECO, AOD, FEVTSIM, RECOSIM, AODSIM.
AlCaReco.cfg: Example config file to generate ALCaReco samples
- Input File: edit filenames to match input file
- Output Files: multiple AlCaReco streams
- path and endpath must be (de)selected according to the wanted AlCaReco stream
copy.cfg: Example config file to copy a fraction of a data set locally
- Input File: edit filenames to match input file
- Output File: local file mycopy.root
GenPythiaGunJpsiExample.cfg: Example config file to run PythiaSource in the "particle gun" mode; generates J/psi and runs Pythia6 to decay them into ee or mumu (random decays turned off")
- Input: PythiaSource configuration
- Output: local file gen_jspi.root"
GenH190ZZ4muExample.cfg: Example cfg to generate H(190)->ZZ->4mu (no UE)
- Input: PythiaSource configuration
- Output: local file pythiaH190ZZ4mu.root
SimDigiStoreRndmExample.cfg: Example cfg to processes H(190)->ZZ->4mu generator particles through Geant4-based detector simulation and detector electronics modeling (digitization); stores state of random engine for each involved module
- Input: local file pythiaH190ZZ4mu.root
- Output: local file H190ZZ4mu_detsim_digi.root
RestoreRndmSimDigiExample.cfg: Example cfg to read pre-simulated sample, skip certain number of events at the beginning, start from specific event, restore random engine states for all modules in the chain, on the event-by-event basis, and re-processes detector simulation and digitization
- Input: local file H190ZZ4mu_detsim_digi.root
- Output: restore_rndm_H190ZZ4mu_detsim_digi.root

Structure

The general structure of a .cfg file is explained here, for the Full Chain case. A .cfg needs the following pieces

A random number service

   service = RandomNumberGeneratorService
   {
      untracked uint32 sourceSeed = 123456789
      PSet moduleSeeds =
      {
         untracked uint32 VtxSmeared = 98765432
	 untracked uint32 g4SimHits  = 11
	 untracked uint32 mix        = 12345   

         untracked uint32 siPixelDigis =1234567
         untracked uint32 siStripDigis =1234567

         untracked uint32 ecalUnsuppressedDigis = 1234567

         untracked uint32 hcalDigis  = 11223344

         untracked uint32 muonCSCDigis  = 11223344
         untracked uint32 muonDTDigis = 1234567
         untracked uint32 muonRPCDigis = 1234567
      }
   }

sourceSeed serves for general purposes use cases, VtxSmeared for vertex smearing, g4SimHits is used for in Geant4 detector simulation, and mix is used in the MixingModule

A source. In these example cases, it is either a PythiaSource or a ParticleGunSource

A PythiaSource contains the parameters passed to Pythia and used to generate the sample. See an example below:

source = PythiaSource 
  {
    untracked int32 maxEvents = 1
    untracked bool pythiaVerbosity = true

    PSet PythiaParameters = 
    {
      # This is a vector of ParameterSet names to be read, in this order
      vstring parameterSets = 
      {
        "pythiaUESettings",
        "pythiaUDSJets"
      }

      # CMS default pythia parameters
      include "Configuration/Generator/data/PythiaUESettings.cfi"

      # all flavour jets (configuration by Thomas Speer)
      vstring pythiaUDSJets = 
      {
        'MSEL=0          ! User defined processes',
        'MSUB(11)=1      ! qq->qq',
        'CKIN(3)=50.     ! Pt hat lower cut',
        'CKIN(4)=120.    ! Pt hat upper cut',
        'CKIN(13)=0.     ! etamin',
        'CKIN(14)=2.5    ! etamax',
        'CKIN(15)=-2.5   ! -etamax',
        'CKIN(16)=0.     ! -etamin'
      }
    }
  }

A ParticleGun Source. You must specify the type, energy, angular range, and much more. You can use a RandomPt or RanndomE source:

  source = FlatRandomPtGunSource 
  { 
    untracked uint32 firstRun  =  1
    untracked int32 maxEvents = 1
    untracked PSet PGunParameters =
    {
      untracked vint32  PartID = {13}
      untracked double MinEta = -2.5
      untracked double MaxEta =  2.5
      untracked double MinPhi = -3.14159265358979323846 # in radians
      untracked double MaxPhi =  3.14159265358979323846
      untracked double MinPt  =  0.999
      untracked double MaxPt  = 1.001
    }
    untracked int32 Verbosity = 0 # set to 1 (or greater)  for printouts
  }

An include to clarify which calibration option to choose. At the moment you have many options:
- FakeConditions.cff, which does not connect to DB but uses some "reasonable" numbers - nothing is miscalibrated or misaligned, hence it represents a perfectly known detector
- FrontierConditions.cff: the condition payloads are the same as those from FakeConditions.cff, but are fetched from Frontier
- Frontier10pbConditions: uses Frontier to simulate a detector miscalibrated and misaligned at the level we expect it to be after 10pb of data
- Frontier100pbConditions: uses Frontier to simulate a detector miscalibrated and misaligned at the level we expect it to be after 100pb of data
```
include "Configuration/StandardSequences/data/FakeConditions.cff"
```

From this point on, you have simply to include and slightly modify lines.

If you want to run reconstruction in the .cfg, you need to include the relevant sequence:
```
include "Configuration/StandardSequences/data/Reconstruction.cff"
```

If you want to run simulation, you need to

include the sequence

include "Configuration/StandardSequences/data/Simulation.cff"

include one Vertex Smearing option (and only one!) among

include "Configuration/StandardSequences/data/VtxSmearedFlat.cff"
include "Configuration/StandardSequences/data/VtxSmearedGauss.cff"
include "Configuration/StandardSequences/data/VtxSmearedNoSmear.cff"
include "Configuration/StandardSequences/data/VtxSmearedBeamProfile.cff"
include "Configuration/StandardSequences/data/VtxSmearedBetafuncNominalCollision.cff"
include "Configuration/StandardSequences/data/VtxSmearedBetafuncEarlyCollision.cff"

please refer to Package Configuration/StandardSequences for a more detailed explanation.

include one PileUp option (and only one!) among

include "Configuration/StandardSequences/data/MixingNoPileUp.cff"
include "Configuration/StandardSequences/data/MixingLowLumiPileUp.cff"
include "Configuration/StandardSequences/data/MixingHighLumiPileUp.cff"

again, refer to Package Configuration/StandardSequences for a more detailed explanation.

You need to setup your path / your paths. For example, in a Full Chain case,
```
path p = {simulation,reconstruction}
```
The only other part missing is the definition of the Output; you need to
- define where to write (e.g. file name)
- define what to write (e.g. whether to write FEVT, RECO, AOD; with or without SIM info) you need to include the Event definition fragment
```
include "Configuration/StandardSequences/data/EventContent.cff"
```
  and then define a PoolOutputModule as in
```
   module FEVT = PoolOutputModule 
   { 
     	using FEVTSIMEventContent
	untracked string fileName = "PhysVal-DiElectron-Ene10.root"
   }
```
  The different options usable for the EventContent are explained in Package Configuration/EventContent.

Simply add the lines

   endpath outpath = {FEVT}
   schedule = {p,outpath}

Last updated: @ Julia Yarba

Generated on Tue Jun 9 17:56:13 2009 for CMSSW by

1.5.4

Package Configuration/Examples

Description

Files

Structure