Note

Click here to download the full example code

# Optimization History View¶

In this example, we illustrate the use of the `OptHistoryView`

plot
on the Sobieski’s SSBJ problem.

```
from __future__ import annotations
from gemseo.api import configure_logger
from gemseo.api import create_discipline
from gemseo.api import create_scenario
from gemseo.problems.sobieski.core.problem import SobieskiProblem
```

## Import¶

The first step is to import some functions from the API and a method to get the design space.

```
configure_logger()
```

```
<RootLogger root (INFO)>
```

## Description¶

The **OptHistoryView** post-processing
creates a series of plots:

The design variables history - This graph shows the normalized values of the design variables, the \(y\) axis is the index of the inputs in the vector; and the \(x\) axis represents the iterations.

The objective function history - It shows the evolution of the objective value during the optimization.

The distance to the best design variables - Plots the vector \(log( ||x-x^*|| )\) in log scale.

The history of the Hessian approximation of the objective - Plots an approximation of the second order derivatives of the objective function \(\frac{\partial^2 f(x)}{\partial x^2}\), which is a measure of the sensitivity of the function with respect to the design variables, and of the anisotropy of the problem (differences of curvatures in the design space).

The inequality constraint history - Portrays the evolution of the values of the constraints. The inequality constraints must be non-positive, that is why the plot must be green or white for satisfied constraints (white = active, red = violated). For an IDF formulation, an additional plot is created to track the equality constraint history.

## Create disciplines¶

At this point we instantiate the disciplines of Sobieski’s SSBJ problem: Propulsion, Aerodynamics, Structure and Mission

```
disciplines = create_discipline(
[
"SobieskiPropulsion",
"SobieskiAerodynamics",
"SobieskiStructure",
"SobieskiMission",
]
)
```

## Create design space¶

We also read the design space from the `SobieskiProblem`

.

```
design_space = SobieskiProblem().design_space
```

## Create and execute scenario¶

The next step is to build an MDO scenario in order to maximize the range, encoded ‘y_4’, with respect to the design parameters, while satisfying the inequality constraints ‘g_1’, ‘g_2’ and ‘g_3’. We can use the MDF formulation, the SLSQP optimization algorithm and a maximum number of iterations equal to 100.

```
scenario = create_scenario(
disciplines,
formulation="MDF",
objective_name="y_4",
maximize_objective=True,
design_space=design_space,
)
scenario.set_differentiation_method()
for constraint in ["g_1", "g_2", "g_3"]:
scenario.add_constraint(constraint, "ineq")
scenario.execute({"algo": "SLSQP", "max_iter": 10})
```

```
INFO - 20:57:24:
INFO - 20:57:24: *** Start MDOScenario execution ***
INFO - 20:57:24: MDOScenario
INFO - 20:57:24: Disciplines: SobieskiAerodynamics SobieskiMission SobieskiPropulsion SobieskiStructure
INFO - 20:57:24: MDO formulation: MDF
INFO - 20:57:24: Optimization problem:
INFO - 20:57:24: minimize -y_4(x_shared, x_1, x_2, x_3)
INFO - 20:57:24: with respect to x_1, x_2, x_3, x_shared
INFO - 20:57:24: subject to constraints:
INFO - 20:57:24: g_1(x_shared, x_1, x_2, x_3) <= 0.0
INFO - 20:57:24: g_2(x_shared, x_1, x_2, x_3) <= 0.0
INFO - 20:57:24: g_3(x_shared, x_1, x_2, x_3) <= 0.0
INFO - 20:57:24: over the design space:
INFO - 20:57:24: +-------------+-------------+-------+-------------+-------+
INFO - 20:57:24: | name | lower_bound | value | upper_bound | type |
INFO - 20:57:24: +-------------+-------------+-------+-------------+-------+
INFO - 20:57:24: | x_shared[0] | 0.01 | 0.05 | 0.09 | float |
INFO - 20:57:24: | x_shared[1] | 30000 | 45000 | 60000 | float |
INFO - 20:57:24: | x_shared[2] | 1.4 | 1.6 | 1.8 | float |
INFO - 20:57:24: | x_shared[3] | 2.5 | 5.5 | 8.5 | float |
INFO - 20:57:24: | x_shared[4] | 40 | 55 | 70 | float |
INFO - 20:57:24: | x_shared[5] | 500 | 1000 | 1500 | float |
INFO - 20:57:24: | x_1[0] | 0.1 | 0.25 | 0.4 | float |
INFO - 20:57:24: | x_1[1] | 0.75 | 1 | 1.25 | float |
INFO - 20:57:24: | x_2 | 0.75 | 1 | 1.25 | float |
INFO - 20:57:24: | x_3 | 0.1 | 0.5 | 1 | float |
INFO - 20:57:24: +-------------+-------------+-------+-------------+-------+
INFO - 20:57:24: Solving optimization problem with algorithm SLSQP:
INFO - 20:57:24: ... 0%| | 0/10 [00:00<?, ?it]
INFO - 20:57:24: ... 20%|██ | 2/10 [00:00<00:00, 40.23 it/sec, obj=-2.12e+3]
WARNING - 20:57:24: MDAJacobi has reached its maximum number of iterations but the normed residual 1.4486313079508508e-06 is still above the tolerance 1e-06.
INFO - 20:57:24: ... 30%|███ | 3/10 [00:00<00:00, 23.21 it/sec, obj=-3.75e+3]
INFO - 20:57:24: ... 40%|████ | 4/10 [00:00<00:00, 16.95 it/sec, obj=-4.01e+3]
WARNING - 20:57:25: MDAJacobi has reached its maximum number of iterations but the normed residual 2.928004141058104e-06 is still above the tolerance 1e-06.
INFO - 20:57:25: ... 50%|█████ | 5/10 [00:00<00:00, 12.89 it/sec, obj=-4.49e+3]
INFO - 20:57:25: ... 60%|██████ | 6/10 [00:00<00:00, 10.92 it/sec, obj=-3.4e+3]
INFO - 20:57:25: ... 80%|████████ | 8/10 [00:01<00:00, 9.31 it/sec, obj=-4.76e+3]
INFO - 20:57:25: ... 100%|██████████| 10/10 [00:01<00:00, 8.11 it/sec, obj=-4.56e+3]
INFO - 20:57:25: ... 100%|██████████| 10/10 [00:01<00:00, 8.08 it/sec, obj=-4.56e+3]
INFO - 20:57:25: Optimization result:
INFO - 20:57:25: Optimizer info:
INFO - 20:57:25: Status: None
INFO - 20:57:25: Message: Maximum number of iterations reached. GEMSEO Stopped the driver
INFO - 20:57:25: Number of calls to the objective function by the optimizer: 12
INFO - 20:57:25: Solution:
INFO - 20:57:25: The solution is feasible.
INFO - 20:57:25: Objective: -3749.8868975554387
INFO - 20:57:25: Standardized constraints:
INFO - 20:57:25: g_1 = [-0.01671296 -0.03238836 -0.04350867 -0.05123129 -0.05681738 -0.13780658
INFO - 20:57:25: -0.10219342]
INFO - 20:57:25: g_2 = -0.0004062839430756249
INFO - 20:57:25: g_3 = [-0.66482546 -0.33517454 -0.11023156 -0.183255 ]
INFO - 20:57:25: Design space:
INFO - 20:57:25: +-------------+-------------+---------------------+-------------+-------+
INFO - 20:57:25: | name | lower_bound | value | upper_bound | type |
INFO - 20:57:25: +-------------+-------------+---------------------+-------------+-------+
INFO - 20:57:25: | x_shared[0] | 0.01 | 0.05989842901423112 | 0.09 | float |
INFO - 20:57:25: | x_shared[1] | 30000 | 59853.73840058666 | 60000 | float |
INFO - 20:57:25: | x_shared[2] | 1.4 | 1.4 | 1.8 | float |
INFO - 20:57:25: | x_shared[3] | 2.5 | 2.527371250092273 | 8.5 | float |
INFO - 20:57:25: | x_shared[4] | 40 | 69.86825198198687 | 70 | float |
INFO - 20:57:25: | x_shared[5] | 500 | 1495.734648986894 | 1500 | float |
INFO - 20:57:25: | x_1[0] | 0.1 | 0.4 | 0.4 | float |
INFO - 20:57:25: | x_1[1] | 0.75 | 0.7521124139939552 | 1.25 | float |
INFO - 20:57:25: | x_2 | 0.75 | 0.7520888531444992 | 1.25 | float |
INFO - 20:57:25: | x_3 | 0.1 | 0.1398000762238233 | 1 | float |
INFO - 20:57:25: +-------------+-------------+---------------------+-------------+-------+
INFO - 20:57:25: *** End MDOScenario execution (time: 0:00:01.253571) ***
{'max_iter': 10, 'algo': 'SLSQP'}
```

## Post-process scenario¶

Lastly, we post-process the scenario by means of the `OptHistoryView`

plot which plots the history of optimization for both objective function,
constraints, design parameters and distance to the optimum.

Tip

Each post-processing method requires different inputs and offers a variety
of customization options. Use the API function
`get_post_processing_options_schema()`

to print a table with
the options for any post-processing algorithm.
Or refer to our dedicated page:
Post-processing algorithms.

```
scenario.post_process("OptHistoryView", save=False, show=True)
```

```
<gemseo.post.opt_history_view.OptHistoryView object at 0x7f317bf51ee0>
```

**Total running time of the script:** ( 0 minutes 2.711 seconds)