v1.7.1

• Added:

  • The base class CycleGroup is now proposed to standardize options for groups that contain a loop. (#516)

• Fixed:

  • Missions can now be defined without route. (#515)

v1.7.0

• Added:

  • Centralized way to set options from configuration file. (#510)

• Fixed:

  • Fix for validity domain checker. (#511)

v1.6.0

• Added:

  • FAST-OAD is now officially compatible with Python 3.10. Support of Python 3.7 has been abandoned. (#496)
  • OpenMDAO group options can now be set from configuration file. (#502)
  • Mission computation:
    • A value for maximum lift coefficient can now be set for climb and cruise segments. (#504)
    • Added the field consumed_fuel, computed for each time step and present in CSV output file. (#505)

• Fixed:

  • Decreased execution time by avoiding unnecessary setup operations. (#503)

v1.5.2

• Added:

  • Added sphinx documentation for source data file generation. (#500)

• Fixed:

  • Fix for climb segment going far too high when asked for optimal altitude in some cases. (#497 and #498)
  • Now accepting upper case distribution names for FAST-OAD plugins. (#499)
  • Now DataFile.from_problem() returns a DataFile instance, and not a VariableList instance. (#494)

v1.5.1

• Fixed:
  • Some warning were issued by pandas when using mission module. (#492)

v1.5.0

• Added:

  • Computation of payload-range data. (#471 and #482)
  • Payload-range plot. (#480)
  • Time-step simulation of takeoff in mission module (#481, #484, #487, #490)
  • Introduced concept of macro-segment, for proposing assembly of several segments as one usable segment. (#488)
  • Segment implementations can now be registered using decorators. (#485)
  • Mission definition can now define a global target fuel consumption. (#467)
  • A FAST-OAD plugin can now come with its own source data files, obtainable using fastoad gen_source_data_file command. (#477)

• Changed:

  • fast-oad (not fast-oad-core) now requires at least fast-oad-cs25 0.1.4. (#475)
  • fast-oad (and fast-oad-core) now requires at least OpenMDAO 3.18. (#483)
  • Variable viewer can now display discrete outputs of type string. (#479)

• Fixed:

  • MissionViewer was not able to show several missions. (#477)
  • Fixed compatibility with OpenMDAO 3.26 (#486)

v1.4.2

• Fixed:
  • Fixed compatibility with Openmdao 3.22. (#464)
  • Now a warning is issued when a nan value is in generated input file from a given data source. (#468)
  • Now FAST-OAD_CS25 0.1.4 is explicitly required. (#475)

v1.4.1

• Fixed:
  • Fixed backward compatibility of bundled missions. (#466)

v1.4.0

• Changed:

  • Added a new series of tutorials. (#426)
  • Enhancements in mission module (#430 and #462), mainly:
    • a parameter with a variable as value can now be associated to a unit and a default value that will be used in the OpenMDAO input declaration (and be in generated input data file).
    • a target parameter can be declared as relative to the start point of the segment by prefixing the parameter name with "delta_"
      when setting a parameter, a minus sign can be put before a variable name to get the opposite value (can be useful with relative values)
    • a parameter can now be set at route or mission level.
    • dISA can now be set in mission definition file with isa_offset.
    • a mission phase can now contain other phases.
    • if a segment parameter (dataclass field) is an array or a list, the associated variable in mission file will be declared with shape_by_conn=True.
    • taxi-out and takeoff are no more automatically set outside of the mission definition file:
      • mission starting point (altitude, speed, mass) can now be set using the "start" segment.
      • the mass input of the mission can be set using the "mass_input" segment. This segment can be anywhere in the mission, though it is expected that fuel consumption in previous segments is mass-independent.
      • if none of the two above solution is used to define a mass input variable, the mission module falls back to behaviour of earlier releases, i.e. the automatic addition of taxi-out and takeoff at beginning of the mission.
  • Upgrade to wop 2.x API. (#453)

• Fixed:

  • Variable viewer was showing only one variable at a time if variable names contained no colon. (#456)
  • Optimization viewer was handling incorrectly bounds with value 0. (#461)

v1.3.5

• Fixed:
  • Deactivated automatic reports from OpenMDAO 3.17+ (can still be driven by environment variable OPENMDAO_REPORTS). (#449)
  • Mass breakdown bar plot now accepts more than 5 datasets. The used color map is now consistent with othe FAST-OAD plots. (#451)