After performing a sensitivity analysis and identifying the Metamodel of Optimal Prognosis (MOP) for every response, you can apply optimization on the MOP to check for possible design improvements.
A MOP result file can be imported or connected to initialize the solver that is integrated in the algorithm systems. Parameter and response registration is handled either automatically or manually by selecting user-defined registration settings.
Further information about methods of metamodelling used in optiSLang can be found here.
Registration Modes
: Parameter and response registration is done automatically by default. New file parameters are registered as system parameters and removed file responses will be unregistered. All responses are displayed in the Outputs table containing the name, reference value and the model including basis and weights.
: Registration of parameters and responses is applied manually. All file parameters are listed in the Inputs table containing the name, reference value and information about importance (filtered, important or constant). Ansys recommends to add only important file parameters as system parameters. All file responses are listed in the Outputs containing the name, reference value, and the model including basis and weights.
MOP boundary handling
: Minimum and maximum values of the MOP sampling are used to check parameter values of the current MOP Solver design. If any parameter value exceeds these sampling bounds the design is failed.
: Lower and upper parameter bounds of the initial sampling system are used to check parameter values of the current MOP Solver design. If any parameter value exceeds these bounds (defined in the parameter manager) the design is failed. This mode is used as the default setting.
: Allow extrapolation for designs exceeding the parameter bounds.
Run Options
This node has general Run Options. The number of supported options is individual for each node.
Standard Slots
Besides the common integration slots the MOP Solver node has the following slots.
| Slot Name | Slot Type | Data Type | Description | ||||
|---|---|---|---|---|---|---|---|
| In | Out | ||||||
| MDBPath | X |  | MOP result file of type *_MOP.bin, *.omdb, *.ascmo. | ||||
Troubleshooting
The support for the MOP classic has been removed, the MOP Solver can no longer process *.bin files. To continue working with the MOP Solver, you must complete the following steps:
Load the *.bin file into a MOP node.
Create a new metamodel file by running the node.
Use the MOP Solver as usual with the resulting *.omdb file.