Off design overhaul

[jkirk5]

Summary

• Modified off-design mission API so that saving and loading json file is optional. Off-design missions now have 2 methods of being used (still requires L2):

  1. Directly run an off-design mission from an AviaryProblem in memory after sizing mission using method call
  2. Load a previously saved AviaryProblem from json format, then use method 1 to execute the off-design mission

• Running an off-design mission has been streamlined into a single method call, combining the separate methods for Fallout and Alternate missions.

• Saving/loading a problem to and from json format have been separated out into method/function calls completely separate from off-design mission creation. Saving the problem is an AviaryProblem method, while loading the problem is a function call that has been added to the Aviary api.

• AviaryProblem.phase_info has been renamed to AviaryProblem.mission_info to clarify what information is actually contained in that variable and match naming convention of pre_mission_info and post_mission_info attributes

Related Issues

• Resolves

Backwards incompatibilities

Existing scripts using off-design will need to be updated to use the new interface

The following variable names have been changed: Mission.Design.FUEL_MASS -> Mission.Summary.FUEL_MASS Mission.Design.FUEL_MASS_REQUIRED -> Mission.Summary.FUEL_MASS+REQUIRED Aircraft.Design.OPERATING_MASS -> Mission.Summary.OPERATING_MASS Mission.Design.ZERO_FUEL_MASS -> Mission.Summary.ZERO_FUEL_MASS

New Dependencies

None

[xjjiang]

In GAST, there are a few input variables related to off design. Examples:

ARNGE(3) = 900., ! Off Design Altitude, Short Range ARNGE(4) = 0., ! Off Design Altitude, Long Range OFALT=0., ! off design mission altitude in feet (0.0) OFEM=.78, ! off design specified mission Mach number

Should they be added to Aviary?

[cmbenne3]

In GAST, there are a few input variables related to off design. Examples:

ARNGE(3) = 900., ! Off Design Altitude, Short Range ARNGE(4) = 0., ! Off Design Altitude, Long Range OFALT=0., ! off design mission altitude in feet (0.0) OFEM=.78, ! off design specified mission Mach number

Should they be added to Aviary?

@xjjiang - I am not super familiar with GASP, but from this information alone I imagine you can get the equivalent behavior by sending an altered phase_info dictionary to run the off design mission in Aviary, so I don't think it's necessary to add these parameters. If you let me know more details about what those parameters do in GASP I can run some tests to see if I can replicate that behavior without adding new variables.