Xun Jiang

Results 44 comments of Xun Jiang

There is no `set_up_trajectory_params` in Aviary.

> need to double check if this issue is resolved It is probably resolved because there is no `set_up_trajectory_params` in Aviary now.

There is no `input_variables.py` in the current Aviary source code.

There is no `Dynamic.Mission.RANGE` but `Dynamic.Mission.DISTANCE`. So, it is likely that it is done already. BTW, there is `Mission.Landing.GROUND_DISTANCE`. So, `ground_distance` may not be the best name.

There is no `test_flops_based_static_analysis.py` as of version 0.9.4.

The third item `Aircraft.Engine.ADDITIONAL_MASS_FRACTION` is fixed in [https://github.com/OpenMDAO/Aviary/pull/684](https://github.com/OpenMDAO/Aviary/pull/684)

By now, unit testing on FLOPS based mass for simple layout and simple wing is done.

By now, unit testing on FLOPS based mass for detailed layout and detailed wing is done.

Convert `NETAW` to `Aircraft.Wing.NUM_INPUT_STATION_DIST`. We don't need it in general but need it for BWB.

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...