Provide a better report to help identify overrides that prevent design variables from correctly impacting the problem.

[Kenneth-T-Moore]

Summary

This is in a response to an issue where the wing aspect ratio, which is calculated in Aviary's height energy geometry from the wing area and span, was overridden with a value from the csv file. When wing area is selected as a design variable, the computed aspect ratio is no longer correct, and this impacts the drag computation.

Aviary's override system is flexible, but it allows you to create a situation like described above. To help the user understand that this might be happening, this PR adds a new section to the override report:

The report uses the OpenMDAO variable relevancy graph to detect when an override interferes with dataflow from the design variables to the constraints and objective. The 'depends on" section shows which design variables are being blocked, and the "impacts" section shows which responses this effects. The "feeds" section shows the components that are using the overriden value instead of the computed value. In this example, the wing area affects the computation of the fuselage wetted area, and this has potential impacts on the mass during flight (which is important for the final objective.)

Related Issues

• Resolves Input files overridding variables that should be calculated. #722

Backwards incompatibilities

None

AI Usage

Disclose any AI usage in this PR, including models used and files affected.