Right now the simulation takes input/configuration variables in a mixture of via the messenger classes and through the main executable via command-line flags. However, these inputs are not well organized. We want to use the following conventions for input/configuration variables:
In G4 main executable: batch job options
RunAction Messenger (via macro): output file and run options
Right now the simulation takes input/configuration variables in a mixture of via the messenger classes and through the main executable via command-line flags. However, these inputs are not well organized. We want to use the following conventions for input/configuration variables: