Old recipes

Complete: 1

CMSSW_3_6_1_patch4

More Less

* Setup your CMSSW area:

cmsrel CMSSW_3_6_1_patch4
  • Go to the src/ directory
 cd CMSSW_3_6_1_patch4/src 
  • Define the CVS repository and all symbols, executables compatible with this version of CMSSW
cmsenv 
scramv1 b 

* Start validating with one of the following examples

cmsRun FastSimulation/Configuration/test/Example_cfg.py 
cmsRun FastSimulation/Configuration/test/IntegrationTest_cfg.py  
cmsRun FastSimulation/Configuration/test/IntegrationTestWithHLT_cfg.py
cmsRun FastSimulation/Configuration/test/IntegrationTestIdealWithHLT_cfg.py
cmsRun FastSimulation/Configuration/test/ExampleWithHLT_GRun_cfg.py 

The files named "Example*" and "IntegrationTestIdealWithHLT" contain MC Ideal conditions, while those named "IntegrationTest" and "IntegrationTestWithHLT" work with MC STARTUP conditions and contain miscalibration and misalignement capability. "ExampleWithHLT_GRun_cfg.py" does not do any reconstruction and is well suited to test and validate L1 and low-lumiHLT

Other executables can be produced with the cmsDriver command. For example:

cmsDriver.py TTbar_Tauola_7TeV_cfi.py -s GEN,FASTSIM --pileup=NoPileUp --geometry DB --conditions=START36_V8::All --eventcontent=FEVTDEBUGHLT --datatier GEN-SIM-DIGI-RECO -n 10 --no_exec
will produce a cmsRun'nable job able to generate and fast-simulate 10 TTbar events according to the CMSSW/Configuration/Generator/python/TTbar_Tauola_7TeV_cfi.py configuration, with startup conditions (global Tag START36_V8). Other configuration for generators can be found in CMSSW/Configuration/Generator/python/.

CMSSW_3_5_8

More Less

* Setup your CMSSW area:

cmsrel CMSSW_3_5_8
  • Go to the src/ directory
 cd CMSSW_3_5_8/src 
  • Define the CVS repository and all symbols, executables compatible with this version of CMSSW
cmsenv 
scramv1 b 

* Start validating with one of the following examples

cmsRun FastSimulation/Configuration/test/Example_cfg.py 
cmsRun FastSimulation/Configuration/test/IntegrationTest_cfg.py  
cmsRun FastSimulation/Configuration/test/IntegrationTestWithHLT_cfg.py
cmsRun FastSimulation/Configuration/test/IntegrationTestIdealWithHLT_cfg.py
cmsRun FastSimulation/Configuration/test/ExampleWithHLT_GRun_cfg.py 

The files named "Example*" and "IntegrationTestIdealWithHLT" contain MC Ideal conditions, while those named "IntegrationTest" and "IntegrationTestWithHLT" work with MC STARTUP conditions and contain miscalibration and misalignement capability. "ExampleWithHLT_GRun_cfg.py" does not do any reconstruction and is well suited to test and validate L1 and low-lumiHLT

Other executables can be produced with the cmsDriver command. For example:

cmsDriver.py TTbar_Tauola_7TeV_cfi.py -s GEN,FASTSIM --pileup=NoPileUp --geometry DB --conditions=START3X_V26::All --eventcontent=FEVTDEBUGHLT --datatier GEN-SIM-DIGI-RECO -n 10 --no_exec
will produce a cmsRun'nable job able to generate and fast-simulate 10 TTbar events according to the CMSSW/Configuration/Generator/python/TTbar_Tauola_7TeV_cfi.py configuration, with startup conditions (global Tag START3X_V26). Other configuration for generators can be found in CMSSW/Configuration/Generator/python/.

CMSSW_3_3_6_patch3 (comparison with Summer09 MC production)

More Less

* Setup your CMSSW area:

cmsrel CMSSW_3_3_6_patch3
  • Go to the src/ directory
 cd CMSSW_3_3_6_patch3/src 
  • Get the latest version of FastSimulation/Configuration (bug-fix to include the jetId)
 addpkg FastSimulation/Configuration V01-12-30 
  • Define the CVS repository and all symbols, executables compatible with this version of CMSSW
cmsenv 
scram b 

* Start validating with one of the following examples

cmsRun FastSimulation/Configuration/test/Example_cfg.py 
cmsRun FastSimulation/Configuration/test/IntegrationTest_cfg.py  
cmsRun FastSimulation/Configuration/test/IntegrationTestWithHLT_cfg.py
cmsRun FastSimulation/Configuration/test/IntegrationTestIdealWithHLT_cfg.py
cmsRun FastSimulation/Configuration/test/ExampleWithHLT_8E29_cfg.py 

The files named "Example*" and "IntegrationTestIdealWithHLT" contain MC Ideal conditions, while those named "IntegrationTest" and "IntegrationTestWithHLT" work with MC STARTUP conditions and contain miscalibration and misalignement capability. "ExampleWithHLT_8E29_cfg.py" does not do any reconstruction and is well suited to test and validate L1 and low-lumiHLT

CMSSW_3_1_4

More Less

CMSSW_3_1_4 can be used out of the box. Standard and High Statistics CMS.RelVal are available.

  • Setup your CMSSW area:
cmsrel CMSSW_3_1_4
  • Go to the src/ directory
 cd CMSSW_3_1_4/src 
  • Define the CVS repository and all symbols, executables compatible with this version of CMSSW
cmsenv 

* Start validating with one of the following examples

cmsRun FastSimulation/Configuration/test/Example_cfg.py 
cmsRun FastSimulation/Configuration/test/IntegrationTest_cfg.py  
cmsRun FastSimulation/Configuration/test/IntegrationTestWithHLT_cfg.py
cmsRun FastSimulation/Configuration/test/IntegrationTestIdealWithHLT_cfg.py
cmsRun FastSimulation/Configuration/test/ExampleWithHLT_8E29_cfg.py 

The files named "Example*" and "IntegrationTestIdealWithHLT" contain MC conditions (MC_31X_V3::All Global conditions tag), while those named "IntegrationTest" and "IntegrationTestWithHLT" work with STARTUP conditions (STARTUP31X _V2::All) and contain miscalibration and misalignement capability. "ExampleWithHLT_8E29_cfg.py" does not do any reconstruction and is well suited to test and validate L1 and low-lumiHLT

CMSSW_3_1_0_pre6

More  Less 

The version of CMSSW_3_1_0_pre6 has a serious problem with muon simulation. It needs additional packages to work properly.

  • Setup your CMSSW area:
cmsrel CMSSW_3_1_0_pre6
  • Go to the src/ directory
 cd CMSSW_3_1_0_pre6/src 
  • Define the CVS repository and all symbols, executables compatible with this version of CMSSW
cmsenv
project CMSSW
To use the standard 3_1_0_pre6 version, just do
addpkg FastSimulation/Calorimetry  V02-02-01 
addpkg FastSimulation/MaterialEffects    V04-05-01 
scramv1 b 

* Start validating with one of the following examples

cmsRun FastSimulation/Configuration/test/Example_cfg.py 
cmsRun FastSimulation/Configuration/test/IntegrationTest_cfg.py 
cmsRun FastSimulation/Configuration/test/IntegrationTestWithHLT_cfg.py
cmsRun FastSimulation/Configuration/test/IntegrationTestIdealWithHLT_cfg.py
cmsRun FastSimulation/Configuration/test/ExampleWithHLT_8E29_cfg.py 

The files named "Example*" and "IntegrationTestIdealWithHLT" containt IDEAL conditions, while those named "IntegrationTest" and "IntegrationTestWithHLT" work with STARTUP conditions, and contain miscalibration and misalignement capability. "ExampleWithHLT_8E29_cfg.py" does not do any reconstruction and is well suited to test and validate L1 and HLT.

CMSSW_3_1_0_pre4

More  Less 

The version of CMSSW_3_1_0_pre4 works out of the box, ready to be validated.

  • Setup your CMSSW area:
cmsrel CMSSW_3_1_0_pre4
  • Go to the src/ directory
 cd CMSSW_3_1_0_pre4/src 
  • Define the CVS repository and all symbols, executables compatible with this version of CMSSW
cmsenv
project CMSSW
To use the standard 3_1_0_pre4 version, just do
addpkg FastSimulation
scramv1 b 

* Start validating with one of the following examples (which run, and are partly validated)

cmsRun FastSimulation/Configuration/test/Example_cfg.py 
cmsRun FastSimulation/Configuration/test/IntegrationTestFake_cfg.py
cmsRun FastSimulation/Configuration/test/IntegrationTest_cfg.py 
cmsRun FastSimulation/Configuration/test/IntegrationTestWithHLT_cfg.py
cmsRun FastSimulation/Configuration/test/IntegrationTestIdealWithHLT_cfg.py
cmsRun FastSimulation/Configuration/test/ExampleWithHLT_cfg.py 

The files named "Example*" and "IntegrationTestFake" work with fake conditions, while those named "IntegrationTest" and "IntegrationTestWithHLT" work with frontier conditions, and contain miscalibration and misalignement capability. The IntegrationTestIdealWithHLT examples also uses frontier, but with ideal conditions. The last one doesn't do any reconstruction and is well suited to test and validate L1 and HLT. In this file, you can even change the prescale factors of the L1 back to no prescaling at all if you want to test easily paths that would be downscaled by default.

CMSSW_3_1_0_pre3

More  Less 

The version of CMSSW_3_1_0_pre3 has a missing feature in a DataFormat. Therefore it is safer to recompile the entire Fast Simulation subsystem.

  • Setup your CMSSW area:
cmsrel CMSSW_3_1_0_pre3
  • Go to the src/ directory
 cd CMSSW_3_1_0_pre3/src 
  • Define the CVS repository and all symbols, executables compatible with this version of CMSSW
cmsenv
project CMSSW
To use the standard 3_1_0_pre3 version, just do
addpkg DataFormats/TrackerRecHit2D V06-01-03
addpkg FastSimulation
scramv1 b 

* Start validating with one of the following examples (which run, and are partly validated)

cmsRun FastSimulation/Configuration/test/Example_cfg.py 
cmsRun FastSimulation/Configuration/test/IntegrationTestFake_cfg.py
cmsRun FastSimulation/Configuration/test/IntegrationTest_cfg.py 
cmsRun FastSimulation/Configuration/test/IntegrationTestWithHLT_cfg.py
cmsRun FastSimulation/Configuration/test/IntegrationTestIdealWithHLT_cfg.py
cmsRun FastSimulation/Configuration/test/ExampleWithHLT_cfg.py 

The files named "Example*" and "IntegrationTestFake" work with fake conditions, while those named "IntegrationTest" and "IntegrationTestWithHLT" work with frontier conditions, and contain miscalibration and misalignement capability. The IntegrationTestIdealWithHLT examples also uses frontier, but with ideal conditions. The last one doesn't do any reconstruction and is well suited to test and validate L1 and HLT. In this file, you can even change the prescale factors of the L1 back to no prescaling at all if you want to test easily paths that would be downscaled by default.

CMSSW_3_1_0_pre2

More  Less 

The version of CMSSW_3_1_0_pre2 has a major bug. The following tags are crucial to make it work correctly.

  • Setup your CMSSW area:
cmsrel CMSSW_3_1_0_pre2
  • Go to the src/ directory
 cd CMSSW_3_1_0_pre2/src 
  • Define the CVS repository and all symbols, executables compatible with this version of CMSSW
cmsenv
project CMSSW
To use the standard 3_1_0_pre2 version, just do
addpkg FastSimulation/TrajectoryManager V01-04-12 
addpkg FastSimulation/ParticleDecay V02-02-02 
addpkg FastSimulation/EventProducer V03-10-12 
addpkg FastSimulation/Event V02-08-00
addpkg FastSimulation/Configuration 
scramv1 b 

* Start validating with one of the following examples (which run, and are partly validated)

cmsRun FastSimulation/Configuration/test/Example_cfg.py 
cmsRun FastSimulation/Configuration/test/IntegrationTestFake_cfg.py
cmsRun FastSimulation/Configuration/test/IntegrationTest_cfg.py 
cmsRun FastSimulation/Configuration/test/IntegrationTestWithHLT_cfg.py
cmsRun FastSimulation/Configuration/test/IntegrationTestIdealWithHLT_cfg.py
cmsRun FastSimulation/Configuration/test/ExampleWithHLT_cfg.py 

The files named "Example*" and "IntegrationTestFake" work with fake conditions, while those named "IntegrationTest" and "IntegrationTestWithHLT" work with frontier conditions, and contain miscalibration and misalignement capability. The IntegrationTestIdealWithHLT examples also uses frontier, but with ideal conditions. The last one doesn't do any reconstruction and is well suited to test and validate L1 and HLT. In this file, you can even change the prescale factors of the L1 back to no prescaling at all if you want to test easily paths that would be downscaled by default.

CMSSW_3_1_0_pre1

More  Less 

The version of CMSSW_3_1_0_pre1 works out of the box. Unfortunately the release manager neglected to include the latest tags. The following version can be used.

  • Setup your CMSSW area:
cmsrel CMSSW_3_1_0_pre1
  • Go to the src/ directory
 cd CMSSW_3_1_0_pre1/src 
  • Define the CVS repository and all symbols, executables compatible with this version of CMSSW
cmsenv
project CMSSW
To use the standard 3_1_0_pre1 version, just do
addpkg FastSimulation/Configuration 
scramv1 b 
If you are interested in the latest developments, you should rather do:
addpkg DataFormats/EgammaReco V00-10-01
addpkg FastSimulation/CaloRecHitsProducer V05-04-00
addpkg FastSimulation/Configuration  V01-11-01
addpkg FastSimulation/EgammaElectronAlgos V00-08-00
addpkg FastSimulation/HighLevelTrigger V04-07-11
addpkg HLTrigger/Configuration V01-08-02
addpkg HLTrigger/Egamma V00-04-37
addpkg JetMETCorrections/TauJet V02-03-05
addpkg RecoEgamma/Configuration V00-03-00
addpkg RecoEgamma/EgammaElectronAlgos V00-13-00
addpkg RecoEgamma/EgammaElectronProducers V00-16-00
addpkg RecoEgamma/EgammaHLTAlgos V00-04-04
addpkg RecoEgamma/EgammaHLTProducers V00-04-06
addpkg RecoEgamma/EgammaPhotonProducers V04-00-00
addpkg RecoEgamma/Examples V01-02-00

* Start validating with one of the following examples (which run, and are partly validated)

cmsRun FastSimulation/Configuration/test/Example_cfg.py 
cmsRun FastSimulation/Configuration/test/IntegrationTestFake_cfg.py
cmsRun FastSimulation/Configuration/test/IntegrationTest_cfg.py 
cmsRun FastSimulation/Configuration/test/IntegrationTestWithHLT_cfg.py
cmsRun FastSimulation/Configuration/test/IntegrationTestIdealWithHLT_cfg.py
cmsRun FastSimulation/Configuration/test/ExampleWithHLT_cfg.py 

The files named "Example*" and "IntegrationTestFake" work with fake conditions, while those named "IntegrationTest" and "IntegrationTestWithHLT" work with frontier conditions, and contain miscalibration and misalignement capability. The IntegrationTestIdealWithHLT examples also uses frontier, but with ideal conditions. The last one doesn't do any reconstruction and is well suited to test and validate L1 and HLT. In this file, you can even change the prescale factors of the L1 back to no prescaling at all if you want to test easily paths that would be downscaled by default.

CMSSW_3_0_0_pre7

More  Less  * Setup your CMSSW area:
cmsrel CMSSW_3_0_0_pre7
  • Go to the src/ directory
 cd CMSSW_3_0_0_pre7/src 
  • Define the CVS repository and all symbols, executables compatible with this version of CMSSW
 cmsenv
project CMSSW
cvs co -r V01-09-01 FastSimulation/Configuration 
cvs co -r V04-07-10 FastSimulation/HighLevelTrigger
scramv1 b 

  • Start validating with one of the following examples (which run, and are partly validated)
cmsRun FastSimulation/Configuration/test/Example_cfg.py 
cmsRun FastSimulation/Configuration/test/IntegrationTestFake_cfg.py
cmsRun FastSimulation/Configuration/test/IntegrationTest_cfg.py 
cmsRun FastSimulation/Configuration/test/IntegrationTestWithHLT_cfg.py
cmsRun FastSimulation/Configuration/test/IntegrationTestIdealWithHLT_cfg.py
cmsRun FastSimulation/Configuration/test/ExampleWithHLT_cfg.py 

CMSSW_3_0_0_pre6

More  Less 

  • FastSimulation in 3_0_0_pre6 runs out of the box. Ready for validation (NOTE: tuning to new features in the Full Simulation/Reco in progress ).
  • Setup your CMSSW area:
cmsrel CMSSW_3_0_0_pre6
  • Go to the src/ directory
 cd CMSSW_3_0_0_pre6/src 
  • Define the CVS repository and all symbols, executables compatible with this version of CMSSW
 cmsenv
project CMSSW
addpkg FastSimulation/Configuration 
scramv1 b 

  • Start validating with one of the following examples (which run, and are partly validated)
cmsRun FastSimulation/Configuration/test/Example_cfg.py 
cmsRun FastSimulation/Configuration/test/IntegrationTestFake_cfg.py
cmsRun FastSimulation/Configuration/test/IntegrationTest_cfg.py 
cmsRun FastSimulation/Configuration/test/IntegrationTestWithHLT_cfg.py
cmsRun FastSimulation/Configuration/test/IntegrationTestIdealWithHLT_cfg.py
cmsRun FastSimulation/Configuration/test/ExampleWithHLT_cfg.py 

CMSSW_2_2_13

More Less

  • In CMSSW_2_2_13 Fast Simulation works out-of-the-box.
  • Setup your CMSSW area:
cmsrel CMSSW_2_2_13
  • Go to the src/ directory
 cd CMSSW_2_2_13/src 
  • Define the CVS repository and all symbols, executables compatible with this version of CMSSW
 cmsenv
project CMSSW
addpkg FastSimulation/Configuration 
scramv1 b 

  • Start validating with one of the following examples (which run, and are partly validated)
cmsRun FastSimulation/Configuration/test/Example_cfg.py 
cmsRun FastSimulation/Configuration/test/IntegrationTestFake_cfg.py
cmsRun FastSimulation/Configuration/test/IntegrationTest_cfg.py 
cmsRun FastSimulation/Configuration/test/IntegrationTestWithHLT_cfg.py
cmsRun FastSimulation/Configuration/test/IntegrationTestIdealWithHLT_cfg.py
cmsRun FastSimulation/Configuration/test/ExampleWithHLT_cfg.py 

The files named "Example*" and "IntegrationTestFake" work with fake conditions, while those named "IntegrationTest" and "IntegrationTestWithHLT" work with frontier conditions, and contain miscalibration and misalignement capability. The IntegrationTestIdealWithHLT examples also uses frontier, but with ideal conditions. The last one doesn't do any reconstruction and is well suited to test and validate L1 and HLT. In this file, you can even change the prescale factors of the L1 back to no prescaling at all if you want to test easily paths that would be downscaled by default.

CMSSW_2_2_3

More  Less 

  • In CMSSW_2_2_3 Fast Simulation works out-of-the-box: ready for Validation under IDEAL conditions.
  • Setup your CMSSW area:
cmsrel CMSSW_2_2_3
  • Go to the src/ directory
 cd CMSSW_2_2_3/src 
  • Define the CVS repository and all symbols, executables compatible with this version of CMSSW
 cmsenv
project CMSSW
addpkg FastSimulation/Configuration V01-07-95-25
scramv1 b 
(the version from the release is fine as well, but the IDEALV9 frontier conditions has a bug, see the notes below)

  • Start validating with one of the following examples (which run, and are partly validated)
cmsRun FastSimulation/Configuration/test/Example_cfg.py 
cmsRun FastSimulation/Configuration/test/IntegrationTestFake_cfg.py
cmsRun FastSimulation/Configuration/test/IntegrationTest_cfg.py 
cmsRun FastSimulation/Configuration/test/IntegrationTestWithHLT_cfg.py
cmsRun FastSimulation/Configuration/test/IntegrationTestIdealWithHLT_cfg.py
cmsRun FastSimulation/Configuration/test/ExampleWithHLT_cfg.py 

The files named "Example*" and "IntegrationTestFake" work with fake conditions, while those named "IntegrationTest" and "IntegrationTestWithHLT" work with frontier conditions, and contain miscalibration and misalignement capability. The IntegrationTestIdealWithHLT examples also uses frontier, but with ideal conditions. The last one doesn't do any reconstruction and is well suited to test and validate L1 and HLT. In this file, you can even change the prescale factors of the L1 back to no prescaling at all if you want to test easily paths that would be downscaled by default.

Notes

  • A problem with the IDEALV9 conditions has been found, if your config file is using frontier, you should use V11 instead
  • The cmsDriver using "startup" conditions has not been validated yet.

CMSSW_2_2_1

More  Less 

  • In CMSSW_2_2_1 Fast Simulation works out-of-the-box: ready for Validation under IDEAL conditions.
  • Setup your CMSSW area with the latest integration build:
scramv1 project CMSSW CMSSW_2_2_1
  • Go to the src/ directory
 cd CMSSW_2_2_1/src 
  • Define the CVS repository and all symbols, executables compatible with this version of CMSSW
 cmsenv
addpkg FastSimulation/Muons V00-01-08-02 
addpkg FastSimulation/Tracking V04-07-03-09
addpkg FastSimulation/Configuration V01-07-95-21
addpkg FastSimulation/TrajectoryManager V01-04-09
addpkg FastSimulation/MaterialEffects V04-03-10
addpkg FastSimulation/MuonSimHitProducer V00-02-08 
addpkg FastSimulation/Calorimetry V02-01-03 
addpkg FastSimulation/CaloRecHitsProducer V05-03-21 
addpkg FastSimulation/ParticlePropagator    V01-02-02
scramv1 b 

  • Start validating with one of the following examples (which run, and are partly validated)
cmsRun FastSimulation/Configuration/test/Example_cfg.py 
cmsRun FastSimulation/Configuration/test/IntegrationTestFake_cfg.py
cmsRun FastSimulation/Configuration/test/IntegrationTest_cfg.py 
cmsRun FastSimulation/Configuration/test/IntegrationTestWithHLT_cfg.py
cmsRun FastSimulation/Configuration/test/ExampleWithHLT_cfg.py 

The files named "Example*" and "IntegrationTestFake" work with fake conditions, while those named "IntegrationTest" and "IntegrationTestWithHLT" work with frontier conditions, and contain miscalibration and misalignement capability. The last one doesn't do any reconstruction and is well suited to test and validate L1 and HLT. In this file, you can even change the prescale factors of the L1 back to no prescaling at all if you want to test easily paths that would be downscaled by default.

Note, the cmsDriver using "startup" conditions is broken.

CMSSW_2_2_0

More  Less 

  • In CMSSW_2_2_0 Fast Simulation works out-of-the-box: ready for Validation under IDEAL conditions.
  • Setup your CMSSW area with the latest integration build:
scramv1 project CMSSW CMSSW_2_2_0
  • Go to the src/ directory
 cd CMSSW_2_2_0/src 
  • Define the CVS repository and all symbols, executables compatible with this version of CMSSW
 cmsenv
addpkg FastSimulation/Configuration V01-07-95-20
addpkg FastSimulation/Tracking V04-07-03-06
addpkg FastSimulation/EgammaElectronAlgos V00-07-23
addpkg FastSimulation/HighLevelTrigger V00-04-02-02
addpkg FastSimulation/Muons V00-01-08-02 
scramv1 b 
and to get the latest improvements (HCAL noise simulation and new tuned shower parameterization):
addpkg FastSimulation/EventProducer
addpkg FastSimulation/CaloHitMakers
addpkg FastSimulation/Calorimetry V02-01-01
addpkg FastSimulation/ShowerDevelopment  V02-03-00
addpkg FastSimulation/CaloRecHitsProducer V05-03-18
scramv1 b 

  • Start validating with one of the following examples (which run, and are partly validated)
cmsRun FastSimulation/Configuration/test/Example_cfg.py 
cmsRun FastSimulation/Configuration/test/IntegrationTestFake_cfg.py
cmsRun FastSimulation/Configuration/test/IntegrationTest_cfg.py 
cmsRun FastSimulation/Configuration/test/IntegrationTestWithHLT_cfg.py
cmsRun FastSimulation/Configuration/test/ExampleWithHLT_cfg.py 

The files named "Example*" and "IntegrationTestFake" work with fake conditions, while those named "IntegrationTest" and "IntegrationTestWithHLT" work with frontier conditions, and contain miscalibration and misalignement capability. The last one doesn't do any reconstruction and is well suited to test and validate L1 and HLT. In this file, you can even change the prescale factors of the L1 back to no prescaling at all if you want to test easily paths that would be downscaled by default.

Note, the cmsDriver using "startup" conditions is broken.

CMSSW_2_2_0_pre1

More  Less 
  • In CMSSW_2_2_0_pre1 Fast Simulation works out-of-the-box: ready for Validation under IDEAL conditions. The following tags are needed for the startup conditions
  • Setup your CMSSW area with the latest integration build:
scramv1 project CMSSW CMSSW_2_2_0_pre1
  • Go to the src/ directory
 cd CMSSW_2_2_0_pre1/src 
  • Define the CVS repository and all symbols, executables compatible with this version of CMSSW
 cmsenv
cvs co -r  V01-07-95-14 FastSimulation/Configuration 
cvs co -r V04-07-03-01 FastSimulation/Tracking 
scramv1 b 

  • Start validating with one of the following examples (which run, and are partly validated)
cmsRun FastSimulation/Configuration/test/Example_cfg.py 
cmsRun FastSimulation/Configuration/test/IntegrationTestFake_cfg.py
cmsRun FastSimulation/Configuration/test/IntegrationTest_cfg.py 
cmsRun FastSimulation/Configuration/test/IntegrationTestWithHLT_cfg.py
cmsRun FastSimulation/Configuration/test/ExampleWithHLT_cfg.py 

The files named "Example*" and "IntegrationTestFake" work with fake conditions, while those named "IntegrationTest" and "IntegrationTestWithHLT" work with frontier conditions, and contain miscalibration and misalignement capability. The last one doesn't do any reconstruction and is well suited to test and validate L1 and HLT. In this file, you can even change the prescale factors of the L1 back to no prescaling at all if you want to test easily paths that would be downscaled by default.

CMSSW_2_1_9

More  Less  In CMSSW_2_1_9 Fast Simulation works out-of-the-box: ready for Validation.
  • Setup your CMSSW area with the latest integration build:
scramv1 project CMSSW CMSSW_2_1_9
  • Go to the src/ directory
 cd CMSSW_2_1_9/src 
  • Define the CVS repository and all symbols, executables compatible with this version of CMSSW
 eval `scramv1 runtime -(c)sh` 
addpkg FastSimulation/Configuration
scramv1 b python

CMSSW_2_1_8

More  Less 
  • Setup your CMSSW area with the latest integration build:
scramv1 project CMSSW CMSSW_2_1_8
  • Go to the src/ directory
 cd CMSSW_2_1_8/src 
  • Define the CVS repository and all symbols, executables compatible with this version of CMSSW
 eval `scramv1 runtime -(c)sh` 
cvs co -r V01-07-81 FastSimulation/Configuration
cvs co -r V00-03-02-01 RecoTauTag/TauTagTools
addpkg JetMETCorrections/TauJet
addpkg RecoTauTag/RecoTau
scramv1 b python
* Known problem : the processing time increases with time

CMSSW_2_1_7

See the recipe for CMSSW_2_1_6.

* Known problem : the processing time increases with time

CMSSW_2_1_6

More  Less 
  • In CMSSW_2_1_6 Fast Simulation works out-of-the-box: ready for Validation.
  • Setup your CMSSW area with the latest integration build:
scramv1 project CMSSW CMSSW_2_1_6
  • Go to the src/ directory
 cd CMSSW_2_1_6/src 
  • Define the CVS repository and all symbols, executables compatible with this version of CMSSW
 eval `scramv1 runtime -(c)sh` 
  • Start validating with one of the following examples (which run, and are partly validated)
addpkg FastSimulation/Configuration
scramv1 b python
cmsRun FastSimulation/Configuration/test/Example_cfg.py 
cmsRun FastSimulation/Configuration/test/IntegrationTestFake_cfg.py
cmsRun FastSimulation/Configuration/test/IntegrationTest_cfg.py 
cmsRun FastSimulation/Configuration/test/ExampleWithHLT_cfg.py 
cmsRun FastSimulation/Configuration/test/IntegrationTestWithHLT_cfg.py

Recipe for impatient user CMSSW_1_8_4 (or 1_6_12)

More  Less 

FastSimulation is now ready to be used by impatient users, since its public release announced with CMSSW_1_5_0. You can follow the following list of instructions, and send your feedback to the Fast Simulation Hypernews list if you encounter problems or have questions. The documentation written below works for the CMSSW version mentioned in this recipe. Given the fast developments of FastSimulation, it is more than likely that it won't work for any different version! (See next section for all supported versions/tags.)

  • Setup your CMSSW area:
 scramv1 project CMSSW CMSSW_1_8_4 (or CMSSW_1_6_12)
  • Go to the src/ directory
 cd CMSSW_1_8_4/src (or CMSSW_1_6_12/src)
  • Define the CVS repository and all symbols, executables compatible with this version of CMSSW
 project CMSSW
 eval `scramv1 runtime -(c)sh` 
  • Check out one package where specific configurations can be found and one package to fix a bug in the muon helix propagator
 cvs co -r V01-06-05 TrackPropagation/CMS.SteppingHelixPropagator
  • CMSSW_1_6_12 works out of the box contains the bug fixes for hadron nuclear interactions and the improved single hadron response at high energy.
 addpkg FastSimulation/Configuration 

If you plan to run via CRAB, you should also do the following (see also FAQ)
cvs co -r V00-13-07 FastSimulation/Configuration

and finally compile

scramv1 b

and run one example.

  • In CMSSW_1_8_4, check out and compile four packages with bug fixes for hadron decaying in flight to muons, and for hadron nuclear interactions.
 cvs co -r V02-05-01-08 FastSimulation/Event
cvs co -r V01-04-09-05 FastSimulation/Configuration
cvs co -r  V00-00-04-01 FastSimulation/MuonSimHitProducer
cvs co -r V00-00-08-03 FastSimulation/Muons
cvs co -r V00-00-13-01 FastSimulation/ParamL3MuonProducer 
cvs co -r V04-02-02-01 FastSimulation/MaterialEffects
cvs co -r V05-00-11-01 FastSimulation/CaloRecHitsProducer
cvs co -r V02-00-00-01 FastSimulation/Calorimetry
cvs co -r V01-04-00-03 FastSimulation/TrajectoryManager
addpkg FastSimulation/EventProducer
scramv1 b
  • In CMSSW_1_8_4, you should also copy the following data files for nuclear interaction simulation
  cp /afs/cern.ch/cms/data/CMSSW/FastSimulation/MaterialEffects/data/*Val* FastSimulation/MaterialEffects/data/. 


 
  • Run one example
 cmsRun FastSimulation/Configuration/test/Example.cfg 

In this example, gg -> H -> ZZ -> eeee, eemumu and mumumumu events are generated with PYTHIA, in-time pile-up events are superimposed with an average of five events per bunch crossing, PSimHit's and PCaloHit's are created in the tracker and in the calorimeters, RecHit's are produced in the tracker and the calorimeters. TrackCandidates are produced with the tracker RecHit's and are fitted to form tracks. All sorts of Ecal clusters are produced from the calo RecHit's All this is done with the famosWithTracksAndEcalClusters sequence. Another example, placed in FastSimulation/Configuration/test/IntegrationTest.cfg, produces top pairs with the famosWithEverything sequence. Other self-explanatory sequences can be found in FastSimulation/Configuration/data/FamosSequences.cff and are named

  • famosSimHits (150);
  • famosWithTrackerHits (150);
  • famosWithCaloHits (150);
  • famosWithTracks (150);
  • famosWithTracksAndCaloHits (150);
  • famosWithEcalClusters (150);
  • famosWithTracksAndEcalClusters (150);
  • famosWithCaloTowers (150);
  • famosWithJets (150);
  • famosWithTracksAndCaloTowers (150);
  • famosWithTracksAndJets (150);
  • famosWithParticleFlow (150);
  • famosWithCaloTowersAndParticleFlow (150);
  • famosWithMuons (150);
  • famosWithBTagging (151);
  • famosWithElectrons (151).
  • famosWithTauTagging (160);
  • famosWithPFTauTagging (160);
  • famosWithEverything (160): to be used with care!
  • famosWithPhotons (165)
  • famosWithElectronsAndPhotons (165)
  • famosWithTracksAndMuons (180)
  • famosWithIterativeTracking (180)

In parentheses is indicated the FAMOS tag (and the CMSSW version) from which this sequence is available. Tracker misalignment is available from 151 onwards, Ecal miscalibration from 152 onwards, and Hcal miscalibration from 168 onwards. The famosWithTracksAndMuons sequence is in test for now and should be used by developers only.

The active user will soon develop a need for other sequences. For example, (s)he may want to produce electrons, muons and jets in the same job. All the lego blocks needed to do so are available in FastSimulation/Configuration/data/FamosSequences.cff to produce the relevant sequence. In this particular example, the proper sequence can be defined as

sequence famosWithElectronsAndMuonsAndJets = {
    famosWithTracksAndJets,
    paramMuons,
    ecalClusteringSequence,
    famosElectronSequence
}
and can be used to replace the famosWithTracksAndEcalClusters of the example. The user can then write an EDAnalyser module, and analyse these simulated and reconstructed electrons, muons and jets, by simply adding the EDAnalyser module name to the path p1.

Finally, nothing is written onto the output in this example (because it's much more time consuming than the Fast Simulation itself!), but it is up to the user to add uncomment to corresponding line in the configuration file. The user can also write his/her own EDAnalyser to read the event content at this point.

  • More examples (in CMSSW_1_8_4 only)
cmsRun FastSimulation/Configuration/test/Example.cfg 
cmsRun FastSimulation/Configuration/test/IntegrationTestFake.cfg
cmsRun FastSimulation/Configuration/test/IntegrationTest.cfg
cmsRun FastSimulation/Configuration/test/IntegrationTestWithHLT.cfg
cmsRun FastSimulation/Configuration/test/ExampleWithHLT.cfg

The files named "Example*" and "IntegrationTestFake" work with fake conditions, while those named "IntegrationTest" and "IntegrationTestWithHLT" work with frontier conditions, and contain miscalibration and misalignement capability. The last one doesn't do any reconstruction and is well suited to test and validate L1 and HLT. In this file, you can even change the prescale factors of the L1 back to no prescaling at all if you want to test easily paths that would be downscaled by default.

Review Status

Reviewer/Editor and Date Comments
FlorianBeaudette - 15 Sep 2008 Page creation

Responsible: FlorianBeaudette
Last reviewed by:

Edit | Attach | Watch | Print version | History: r19 < r18 < r17 < r16 < r15 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r19 - 2011-02-02 - AndreaPerrotta



 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    CMSPublic All webs login

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