Changes between Version 12 and Version 13 of WhizardInterface


Ignore:
Timestamp:
03/19/10 11:15:59 (11 years ago)
Author:
ChristianSpeckner
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WhizardInterface

    v12 v13  
    3636It is wise to '''check the messages the interface generates''' while it runs; i these will inform you about any unidentified vertices that have been skipped as well as of most other noteworthy caveats concerning the generated code.
    3737
    38 == Usage: 1.9x particularities ==
     38== Usage: WO 1.9x ==
    3939In order to use the interface with WO 1.9x, the build system of WHIZARD must be patched and the model files copied to the proper locations in the tree. This is taken care of by the script called {{{inject}}} which is created by the interface in the output directory. The basic usage is (from within the output directory):
    4040
     
    4848 * In order for the model to be picked up by WHIZARD, the WO mode name must start with "fr". This is taken care of automatically if the interface assigns it, but if you reset it via {{{WOModelName}}}, it is your responsibility to pick a proper name.
    4949 * Writing multiple models to one output directory is possible and supported.
     50
     51== Usage: WO 2.0 ==
     52WO 2.0 and above natively support the addition of new models without recompiling WHIZARD. More specifically, WHIZARD looks for any model specific files first in the uses local installation tree {{{${HOME}/.whizard}}} and the in the global installation tree {{{${PREFIX}}}}. Therefore, in order to use an external model with WO2, the O'Mega binaries and FORTRAN libraries must be compiled and installed in the proper directory together with the WHIZARD model definition. To the end, the WO interface creates a standard autotoolized (don't worry if you don't know what this means) {{{./configure; make install}}} type build system in the output directory. To use it, you must perform three steps (in the output directory):
     53
     541) Run
     55
     56{{{./configure WO_CONFIG=path_to_the_wo_binaries --prefix=installation_prefix}}}
     57
     58Both options are optional. {{{WO_CONFIG}}} can be used to specify the path to the WHIZARD binaries (otherwise, they are searched for in {{{${PATH}}}}), And {{{--prefix}}} sets the installation prefix for the model files.