Changelog¶

Version 0.5.4-beta¶

Bug fix: An infinite loop could occur if custom modules were declaring the same variable several times with different units or default values.

Added compatibility with OpenMDAO 3.4, which is now the minimum required version of OpenMDAO. (#231)
Simplified call to VariableViewer. (#221)
Bug fix: model for compressibility drag now takes into account sweep angle and thickness ratio. (#237)
Bug fix: at installation, minimum version of Scipy is forced to 1.2. (#219)
Bug fix: SpeedChangeSegment class now accepts Mach number as possible target. (#234)
Bug fix: variable “data:weight:aircraft_empty:mass has now “kg” as unit. (#236)

Added compatibility with OpenMDAO 3.2.
Added the mission performance module (currently computes a fixed standard mission).
Propulsion models are now declared in a specific way so that another module can do a direct call to the needed propulsion model.

Prevents installation of OpenMDAO 3.2 and above for incompatibility reasons.
In Breguet module, output values for climb and descent distances were 1000 times too large (computation was correct, though).

Some changes in mass and performances components:

The Breguet performance model can now be adjusted through input variables in the “settings” section.
The mass-performance loop is now done through the “fastoad.loop.mtow” component.

In Jupyter notebooks, VariableViewer now has a column for input/output type.
Changed base OAD process so that propulsion model can now be directly called by the performance module instead of being a separate OpenMDAO component (which is still possible, though). It prepares the import of FAST legacy mission-based performance model.

Changed dependency requirement to have OpenMDAO version at most 3.1.0 (FAST-OAD is not yet compatible with 3.1.1)