@@ -110,8 +110,22 @@ Multithreading is activated by default, but the user can select how many threads
The `PHYS.VERSION` flag sets the name of the physics class to use in the application:
`PHYS.VERSION = <class_name>` [example: OPTPhys]
Each physics class can include several configuration parameters that are set with the configuration file at runtime. For the user custom physics class, the user decides how to name them.
For the physics classes provided in BoGEMMS-HPC, the parameter name starts with the name of the class.
Each physics class can include several configuration parameters that are set with the configuration file at runtime. For the user custom physics class, the user decides how to name them. The physics class template provides an example on how to create curstom parameters that use the name of the class. E.g. when setting the physics list using the AREMBESPhys physics class:
-`PHYS.VERSION = AREMBESPhys`
-`AREMBESPhys.PHYSLIST = emstandardSS_QBBC`
### Setting the geometry
Writing the mass model to a GDML file:
- activating the writing to GDML file:`GEOM.WRITE.GDML = true/false` (default = false)
- setting the name of the output file: `GEOM.WRITE.GDML.NAME = <name>.gdml`
The `GEOM.VERSION` flag sets the name of the geometry class to use in the application:
The user can create custom parameters in the user geometry class to modify parameters at runtime. See the geometry template for an example on how to add custom parameters. Additional information is provided in the section "Geometry and physics".
For example, to set the default production cut in the `OPTPhys` class:
