Aviary is overwriting the design range with the phase_info's range.

[Kenneth-T-Moore]

Description

This is currently a benchmark failure for test_bench_multiengine.py

In this problem, the Mission.Design.RANGE is specified as 2960 nmi in the csv file, and the phase_info runs a mission using the default hieght_energy file with target range set to 1906 nmi. Sometime during level 2 setup, the Mission.Design.RANGE takes on the 1906 value, regardless of what I set the ProblemTYPE enum.

Example

In test_bench_multiengine.py, specifically the test_multiengine_dynamic and test_multiengine_static tests are failing due to this issue. The smaller (incorrect) design range changes the mass in some component, and leads to different answers for the throttle allocations.

Aviary Version

0.9.4-dev

Relevant environment information

No response