Baseline solution

[jbussemaker]

A baseline solution serves not only to define the input values that characterize the current solution, but also allows the MDAO engineer to verify the robustness and reliability of the assembled MDAO workflow by performing an initial test analysis and comparing the obtained values with the expected values.

If not available:
MDAO user needs to check with MBD engineer if first results are reasonable.
Even worse, the MDAO workflow may seem to work but actually produces wrong outputs.

To be discussed in the global process, shall this be provided by MBD?

[jbussemaker]

From discussion on 2025-12-19:

• Would be similar to providing the "reference solution" as done for the MDAO Sellar problem example
• Additionally there would be the need to provide design vectors and associated outputs for testing the (coupled) analysis models (not just the optimization problem solution)
• Also would be useful on the model-level, because the model behavior should be known before assembling models into a coupled MDAO workflow
• It should also be possible to check values of any outputs (not just objectives/constraints)
• Suggested "types" of baselines:
  • Model-level inputs --> expected output values
  • Coupled MDAO analyses inputs --> expected output values
  • Optimization problem --> expected optimal design vector and output, objective, constraint values