Difference between revisions of "Running GSIM CLAS simulation"
From Hall A Wiki
(→Converting initial data files to GEANT-3 format input) |
|||
| Line 1: | Line 1: | ||
== GSIM Inventory == | == GSIM Inventory == | ||
| − | GSIM directory is to be located on the farm, at a large enough work disk. An example of the simulation inventory can be found at | + | * GSIM directory is to be located on the farm, at a large enough work disk. An example of the simulation inventory can be found at |
| − | /work/halla/e07006/disk1/Erez/GSIM | + | /work/halla/e07006/disk1/Erez/GSIM (will be used for the remainder of the documentation as $GSIM) |
| Line 10: | Line 10: | ||
=== Setting an Event Generator and create events file === | === Setting an Event Generator and create events file === | ||
| + | |||
| + | * PYTHIA is used as the base-line event generator (EG) for GSIM | ||
| + | |||
| + | * The existing EG is a ''fortran'' script located under '''$GSIM/Documents/''' directory. | ||
| + | |||
==== Setting Event Generator ==== | ==== Setting Event Generator ==== | ||
| + | |||
| + | * The EG should be modified for the specific solid target. An example for 12C can be found at | ||
| + | |||
| + | $GSIM/Documents/EventGenerator/src/qp1C.f | ||
| + | |||
| + | * To build the event generator use the build compilation command, e.g. | ||
| + | |||
| + | cd $GSIM/Documents/ | ||
| + | build_EG_cs | ||
| + | |||
| + | (the result would be an executable event generator e.g. '''EventGenerator_exe/EG_C.exe''') | ||
| + | |||
==== Generate the Events ==== | ==== Generate the Events ==== | ||
| + | * Generate the events by executing the EG, e.g. | ||
| + | |||
| + | ./EG_C.exe > test.dat | ||
| + | |||
| + | (the result would be a data file ) | ||
==== Look at the generated distributions ==== | ==== Look at the generated distributions ==== | ||
=== Converting generated data files to GEANT-3 format input === | === Converting generated data files to GEANT-3 format input === | ||
| − | |||
| − | |||
| Line 27: | Line 47: | ||
=== Running generated events through a CLASS GEANT-3 simulation === | === Running generated events through a CLASS GEANT-3 simulation === | ||
| + | === running GSIM with the generated events === | ||
| − | === | + | === Preprocessing to add smearing of the data === |
| + | === Look at the output files === | ||
| + | |||
| + | |||
| + | === Converting the GSIM output file to root === | ||
| + | |||
| + | === Observing the output ROOT TTree === | ||
Revision as of 09:57, 2 March 2015
Contents
- 1 GSIM Inventory
- 2 Running GSIM
- 2.1 Setting an Event Generator and create events file
- 2.2 Converting generated data files to GEANT-3 format input
- 2.3 Running generated events through a CLASS GEANT-3 simulation
- 2.4 running GSIM with the generated events
- 2.5 Preprocessing to add smearing of the data
- 2.6 Look at the output files
- 2.7 Converting the GSIM output file to root
- 2.8 Observing the output ROOT TTree
GSIM Inventory
- GSIM directory is to be located on the farm, at a large enough work disk. An example of the simulation inventory can be found at
/work/halla/e07006/disk1/Erez/GSIM (will be used for the remainder of the documentation as $GSIM)
Running GSIM
Setting an Event Generator and create events file
- PYTHIA is used as the base-line event generator (EG) for GSIM
- The existing EG is a fortran script located under $GSIM/Documents/ directory.
Setting Event Generator
- The EG should be modified for the specific solid target. An example for 12C can be found at
$GSIM/Documents/EventGenerator/src/qp1C.f
- To build the event generator use the build compilation command, e.g.
cd $GSIM/Documents/ build_EG_cs
(the result would be an executable event generator e.g. EventGenerator_exe/EG_C.exe)
Generate the Events
- Generate the events by executing the EG, e.g.
./EG_C.exe > test.dat
(the result would be a data file )
