Deadline for contributions to DecFiles v30r11 is Friday 9th February 2018 at 14:00. Merge requests created after deadline are not guaranteed to be accepted for this release.
Deadline for contributions to DecFiles v30r12 is Friday 9th February 2018 at 14:00. Merge requests created after deadline are not guaranteed to be accepted for this release.
# Steps to add decay file
1. Find if a DecFile you want (or similar enough so you can use it) already exists
...
...
@@ -17,11 +17,11 @@ Deadline for contributions to DecFiles v30r11 is Friday 9th February 2018 at 14:
# Testing a decay file
This is done in three steps:
## Write the decay file and create the options
If you do not already have the environment set up, prepare it to run one of the latest Gauss version (v49rX for Sim09 productions, or v50rX for upgrade productions). In the examples below, v49r8 is used.
If you do not already have the environment set up, prepare it to run one of the latest Gauss version (v49rX for Sim09 productions, or v50rX for upgrade productions). In the examples below, v49r9 is used.
```shell
SetupProject Gauss v49r8--build-env
cd ~/cmtuser/Gauss_v49r8
SetupProject Gauss v49r8
SetupProject Gauss v49r9--build-env
cd ~/cmtuser/Gauss_v49r9
SetupProject Gauss v49r9
```
Then get the Gen/DecFiles package from gitlab.
```shell
...
...
@@ -29,20 +29,20 @@ git lb-clone-pkg Gen/DecFiles
```
Add the new decay file in the dkfiles subdirectory and create the options to be used by Gauss.
```shell
cd ~/cmtuser/Gauss_v49r8/Gen/DecFiles/
cd ~/cmtuser/Gauss_v49r9/Gen/DecFiles/
make
```
If there is no mistake in the decay file, an option file called NNNNNNNN.py is present in the options subdirectory, where NNNNNNNN is the event type number of the decay file. It is also recommended to run the decay file convention parser
```shell
cd ~/cmtuser/Gauss_v49r8/Gen/DecFiles/cmt
cd ~/cmtuser/Gauss_v49r9/Gen/DecFiles/cmt
./decparser.sh ../dkfiles/DecFile.dec
```
This should check for convention correctness for the event type and some basic mistakes, but it also has some limitations. This is our tool to help in checking, but at the end all failures are individually considered. Feel free to email any comments to lhcb-gauss-manager.
## Run Gauss to create a .xgen file
The .xgen file contains the generator level information (both in HepMC and MCParticles format) when running Gauss with only the generator part, without the simulation and Geant4 being activated.