Jason Kirk

I'm trying to figure out what you mean "by the next line" so I can update that. The main installation page doesn't actually contain any specific examples to run besides...

I made a new issue to update documentation and default arguments to functions (https://github.com/OpenMDAO/Aviary/issues/502). I'll close out this issue since the new one covers the main problem with additional instructions...

The chosen path forward on this issue is for VariablesIn and ParamPort to be completely removed

Best way to do this is probably separate out the scaling component that applies the drag factors, and then re-use it for all drag scaling (FLOPS/GASP computation, and FLOPS/GASP tabular...

GASP conversion likely has known problems and new issues should be created as those problems are discovered

Good point, that was poorly worded. More accurately, Aviary desires to support 3 of FLOPS' mass regression equations. Currently we have no plans to port over the fighter regressions -...

To further clarify what we need: Replace "aircraft_type" with a few variable name `Aircraft.Design.AIRCRAFT_TYPE`. That variable should have 3 options set via Enum, TRANSPORT, BLENDED_WING_BODY, and GENERAL_AVIATION. Right now in...

Update: This issue is partially complete. `BLENDED_WING_BODY` is officially a supported transport type. `wing_common.py` does not yet use the proper variable

need to double check if this issue is resolved

This will change model results, and therefore should be a part of the next Aviary version (0.9.6). This can be paired with upcoming changes to openMDAO report locations that will...