Using the MOP Solver Standalone Interface

Complete the following procedure to use the MOP Solver standalone interface.

  1. Initialize the optiSLang monitoring database and create input and output files by running the following command.

    On a Windows system:

    [installation path]\tools\mopsolver\bin\mopsolver.exe [additional options]

    On a Linux system:

    [installation path]/tools/mopsolver/bin/mopsolver [additional options]

    Include all three additional options listed in the following table.

    Program Option Input Description
    --init *.omdb fileReference values of all parameters are extracted and used to calculate the reference response values. These values are used to create input and output files. For initialization of the MOP Solver this option is mandatory.
    --input, -itext file for inputs to be writtenExtracted reference values from optiSLang monitoring database file are written to this file. If this file does not exist, it will be created. This option is mandatory.
    --output, -otext file for outputs to be writtenExtracted reference input values from optiSLang monitoring database file and corresponding output values of the metamodel are written to this file. If this file does not exist, it will be created. This option is mandatory.

    A file named limits.txt containing parameter and response bounds, as well as the CoP matrix is written to the current working directory. Log messages can be found in the (p)mopsolver.log file of the current working directory.

  2. Solve the variation of parameter combinations. The input file with the current design is read and output values that are solved by the metamodel are written to the output file. By default, designs with parameter values outside their bounds cause an error. Such designs can be extrapolated in extended mode.

    To complete this step, run the same command used in the previous step and include the additional options listed in the following table.

    Program Option Input Description
    --input, -itext file for inputs to be readThis file contains the design to be solved. This option is mandatory.
    --output, -otext file for outputs to be writtenThe approximated design containing parameter and responses are written to this file. This option is mandatory.
    --extended-This mode allows input parameter to exceed MOP sampling bounds. In default mode input values are checked before approximation and the application ends with an error. This option will be ignored in init mode.

For more information, include the following optiions:

  • [--help, -h] Show brief help

  • [--version, -v] Show version information