Optimization APIs

This section discusses the APIs provided by ACT to customize DesignXplorer optimization functionality.

Optimization Architecture

The object OptimizationEngineMgr is responsible for the execution of the optimization. Regardless of whether the optimizer is built-in or external, it executes the same process via the optimization API.

The following figure shows the DesignXplorer optimization architecture.

 

The main elements of the API are:

  • IOptimizationMethod: The main interface between DesignXplorer and the external optimizer, which is required to implement it

  • IOptimizationServices: The interface for the external optimizer to access DesignXplorer services, such as the calculation of one or more points

  • DXOptimizationPoint: The class that describes and stores the points data, such as variable values, calculation state, and so on.

For more information, see the "API Description" section in the ANSYS ACT API Reference Guide.

Optimization Process

The object OptimizationEngineMgr drives the optimization process as shown in the following sequence diagram.

 

First, the optimization process retrieves an instance of the optimizer through the callback declared in the extension. It provides the object Services and transfers the complete optimization study definition, which includes all variables, parameter relationships, objectives, constraints, and settings.

The object OptimizationEngineMgr retrieves an instance of the optimizer each time the optimization process is started by invoking the callback OnCreate. The object OptimizationEngineMgr releases the instance on completion by invoking the callback OnRelease.

After a final check CanRun, the optimizer's method Run is invoked. From this point in the sequence, the external optimizer triggers the calculation of points as needed and pushes progress messages, history points, convergence values, and log messages, depending on its capabilities.


Release 18.2 - © ANSYS, Inc. All rights reserved.