Skip to content

GitLab

Last edited by Martin Gabelmann
Page history

WHIZARD

WHIZARD

To generate model files for WHIZARD 

ModelOutput[$EIGENSTATES, WriteWHIZARD->True]

is used.If the vertices have been calculated already by MakeVertexList,

MakeWHIZARD[options]

can be used. The possible options are

  1. WriteOmega, Values: True or False, Default: True Defines, if the model files for Omega should be written
  2. WriteWHIZARD, Values: True or False, Default: True Defines, if the model files for WHIZARD should be written
  3. Exclude, Values: list of generic type, Default: {SSSS} Defines, which generic diagrams are excluded when writing the model file
  4. WOModelName, Values: string, Default: defined model name Gives the possibility to change the model name
  5. MaximalCouplingsPerFile, Values: Number, Default: 500 Defines the maximal number of couplings written in one file
  6. Version, Values: Number, Default: 2.0.3 Defines the version of WHIZARD for which the model file is generated
  7. ReadLists, Values: True or False, Default: False Defines, if the information from a former evaluation should be used
Using the generated model files with WHIZARD 

After the interface has completed, the generated files can be found in the WHIZARD_Omega subdirectory of SARAH s output directory. In order to use the model with WHIZARD 2.x, the generated code must be compiled and installed. For most applications, this is done by simply issuing (inside the output directory)

./configure
make
make install

By default, the third command installs the compiled model into .whizard in current user’s home directory where it is automatically picked up by WHIZARD . Alternative installation paths can be specified using the --prefix option to WHIZARD.

./configure --prefix=/path/to/installation/prefix

If the files are installed into the WHIZARD installation prefix, the program will also pick them up automatically, while WHIZARD ’s --localprefix option must be used to communicate any other choice to WHIZARD . In case WHIZARD is not available in the binary search path, the WO_CONFIG environment variable can be used to point configure to the binaries

./configure WO_CONFIG=/path/to/whizard/binaries

More information on the available options and their syntax can be obtained with the --help option.

In the case of WHIZARD 1.x output, the generated files must be patched into the WHIZARD source tree. To this end, the interface creates a script called inject. In most cases, it is sufficient to simply call the script as

./inject /path/to/whizard

(from within the output directory). Issuing ./inject --help will display a list of options which can be used to adapt the script to more complicated usage scenarios.

See also