Pareto front

In this example, we illustrate the use of the ParetoFront plot on the Sobieski’s SSBJ problem.

from __future__ import annotations

from gemseo import configure_logger
from gemseo import create_discipline
from gemseo import create_scenario
from gemseo.problems.sobieski.core.problem import SobieskiProblem

Import

The first step is to import a high-level function for logging.

configure_logger()

<RootLogger root (INFO)>

Description

The ParetoFront post-processing generates a plot or a matrix of plots (if there are more than 2 objectives). It indicates in red the locally non-dominated points for the current objectives, and in green the globally (all objectives) Pareto optimal points.

Create disciplines

At this point, we instantiate the disciplines of Sobieski’s SSBJ problem: SobieskiPropulsion, SobieskiAerodynamics, SobieskiStructure and SobieskiMission.

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 - 16:12:08:
    INFO - 16:12:08: *** Start MDOScenario execution ***
    INFO - 16:12:08: MDOScenario
    INFO - 16:12:08:    Disciplines: SobieskiAerodynamics SobieskiMission SobieskiPropulsion SobieskiStructure
    INFO - 16:12:08:    MDO formulation: MDF
    INFO - 16:12:08: Optimization problem:
    INFO - 16:12:08:    minimize -y_4(x_shared, x_1, x_2, x_3)
    INFO - 16:12:08:    with respect to x_1, x_2, x_3, x_shared
    INFO - 16:12:08:    subject to constraints:
    INFO - 16:12:08:       g_1(x_shared, x_1, x_2, x_3) <= 0.0
    INFO - 16:12:08:       g_2(x_shared, x_1, x_2, x_3) <= 0.0
    INFO - 16:12:08:       g_3(x_shared, x_1, x_2, x_3) <= 0.0
    INFO - 16:12:08:    over the design space:
    INFO - 16:12:08:    +-------------+-------------+-------+-------------+-------+
    INFO - 16:12:08:    | name        | lower_bound | value | upper_bound | type  |
    INFO - 16:12:08:    +-------------+-------------+-------+-------------+-------+
    INFO - 16:12:08:    | x_shared[0] |     0.01    |  0.05 |     0.09    | float |
    INFO - 16:12:08:    | x_shared[1] |    30000    | 45000 |    60000    | float |
    INFO - 16:12:08:    | x_shared[2] |     1.4     |  1.6  |     1.8     | float |
    INFO - 16:12:08:    | x_shared[3] |     2.5     |  5.5  |     8.5     | float |
    INFO - 16:12:08:    | x_shared[4] |      40     |   55  |      70     | float |
    INFO - 16:12:08:    | x_shared[5] |     500     |  1000 |     1500    | float |
    INFO - 16:12:08:    | x_1[0]      |     0.1     |  0.25 |     0.4     | float |
    INFO - 16:12:08:    | x_1[1]      |     0.75    |   1   |     1.25    | float |
    INFO - 16:12:08:    | x_2         |     0.75    |   1   |     1.25    | float |
    INFO - 16:12:08:    | x_3         |     0.1     |  0.5  |      1      | float |
    INFO - 16:12:08:    +-------------+-------------+-------+-------------+-------+
    INFO - 16:12:08: Solving optimization problem with algorithm SLSQP:
    INFO - 16:12:08: ...   0%|          | 0/10 [00:00<?, ?it]
    INFO - 16:12:08: ...  10%|█         | 1/10 [00:00<00:00, 11.05 it/sec, obj=-536]
    INFO - 16:12:08: ...  20%|██        | 2/10 [00:00<00:01,  7.96 it/sec, obj=-2.12e+3]
 WARNING - 16:12:08: MDAJacobi has reached its maximum number of iterations but the normed residual 1.7130677857005655e-05 is still above the tolerance 1e-06.
    INFO - 16:12:08: ...  30%|███       | 3/10 [00:00<00:01,  6.81 it/sec, obj=-3.75e+3]
    INFO - 16:12:08: ...  40%|████      | 4/10 [00:00<00:00,  6.54 it/sec, obj=-3.96e+3]
    INFO - 16:12:09: ...  50%|█████     | 5/10 [00:00<00:00,  6.38 it/sec, obj=-3.96e+3]
    INFO - 16:12:09: ...  60%|██████    | 6/10 [00:00<00:00,  6.31 it/sec, obj=-4e+3]
    INFO - 16:12:09: ...  70%|███████   | 7/10 [00:01<00:00,  6.88 it/sec, obj=-3.98e+3]
    INFO - 16:12:09: ...  80%|████████  | 8/10 [00:01<00:00,  7.35 it/sec, obj=-3.97e+3]
    INFO - 16:12:09: ...  90%|█████████ | 9/10 [00:01<00:00,  7.77 it/sec, obj=-3.97e+3]
    INFO - 16:12:09: ... 100%|██████████| 10/10 [00:01<00:00,  8.14 it/sec, obj=-3.96e+3]
    INFO - 16:12:09: Optimization result:
    INFO - 16:12:09:    Optimizer info:
    INFO - 16:12:09:       Status: None
    INFO - 16:12:09:       Message: Maximum number of iterations reached. GEMSEO Stopped the driver
    INFO - 16:12:09:       Number of calls to the objective function by the optimizer: 12
    INFO - 16:12:09:    Solution:
    INFO - 16:12:09:       The solution is feasible.
    INFO - 16:12:09:       Objective: -3963.408265187933
    INFO - 16:12:09:       Standardized constraints:
    INFO - 16:12:09:          g_1 = [-0.01806104 -0.03334642 -0.04424946 -0.0518346  -0.05732607 -0.13720865
    INFO - 16:12:09:  -0.10279135]
    INFO - 16:12:09:          g_2 = 3.333278582928756e-06
    INFO - 16:12:09:          g_3 = [-7.67181773e-01 -2.32818227e-01  8.30379541e-07 -1.83255000e-01]
    INFO - 16:12:09:       Design space:
    INFO - 16:12:09:       +-------------+-------------+---------------------+-------------+-------+
    INFO - 16:12:09:       | name        | lower_bound |        value        | upper_bound | type  |
    INFO - 16:12:09:       +-------------+-------------+---------------------+-------------+-------+
    INFO - 16:12:09:       | x_shared[0] |     0.01    | 0.06000083331964572 |     0.09    | float |
    INFO - 16:12:09:       | x_shared[1] |    30000    |        60000        |    60000    | float |
    INFO - 16:12:09:       | x_shared[2] |     1.4     |         1.4         |     1.8     | float |
    INFO - 16:12:09:       | x_shared[3] |     2.5     |         2.5         |     8.5     | float |
    INFO - 16:12:09:       | x_shared[4] |      40     |          70         |      70     | float |
    INFO - 16:12:09:       | x_shared[5] |     500     |         1500        |     1500    | float |
    INFO - 16:12:09:       | x_1[0]      |     0.1     |         0.4         |     0.4     | float |
    INFO - 16:12:09:       | x_1[1]      |     0.75    |         0.75        |     1.25    | float |
    INFO - 16:12:09:       | x_2         |     0.75    |         0.75        |     1.25    | float |
    INFO - 16:12:09:       | x_3         |     0.1     |  0.1562448753887276 |      1      | float |
    INFO - 16:12:09:       +-------------+-------------+---------------------+-------------+-------+
    INFO - 16:12:09: *** End MDOScenario execution (time: 0:00:01.247554) ***

{'max_iter': 10, 'algo': 'SLSQP'}

Post-process scenario

Lastly, we post-process the scenario by means of the ParetoFront.

Tip

Each post-processing method requires different inputs and offers a variety of customization options. Use the high-level 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("ParetoFront", objectives=["g_3", "-y_4"], save=False, show=True)

<gemseo.post.pareto_front.ParetoFront object at 0x7f1767cb0bb0>