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 some high-level functions and a method to get the design space.

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

{'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)

/home/docs/checkouts/readthedocs.org/user_builds/gemseo/envs/5.0.0/lib/python3.9/site-packages/genson/schema/strategies/base.py:42: UserWarning: Schema incompatible. Keyword 'description' has conflicting values ('The width and height of the figure in inches, e.g. ``(w, h)``.\nIf ``None``, use the :attr:`.OptPostProcessor.DEFAULT_FIG_SIZE`\nof the post-processor.' vs. 'The width and height of the figure in inches, e.g. `(w, h)`.\nIf ``None``, use the :attr:`.OptPostProcessor.DEFAULT_FIG_SIZE`\nof the post-processor.'). Using 'The width and height of the figure in inches, e.g. ``(w, h)``.\nIf ``None``, use the :attr:`.OptPostProcessor.DEFAULT_FIG_SIZE`\nof the post-processor.'
  warn(('Schema incompatible. Keyword {0!r} has conflicting '

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