Investiate per mission vs per aircraft variables #1048
Description
Desired capability or behavior.
Aviary has inconsistently translated the FLOPS $MISSIN variables as follows:
FACT -> Mission.FUEL_FLOW_SCALER (this is modifiable separately for each mission a sized aircraft flies)
FCDO - > Aircraft.Design.ZERO_LIFT_DRAG_COEFF_FACTOR
FCDI -> Aircraft.Design.LIFT_DEPENDENT_DRAG_COEFF_FACTOR
FCDSUB -> Aircraft.Design.SUBSONIC_DRAG_COEFF_FACTOR
FCDSUP -> Aircraft.Design.SUPERSONIC_DRAG_COEFF_FACTOR
In FLOPS all of these values are variable per mission.
In Aviary the fuel flow is, but the aerodynamic variables are not.
We should be consistent:
- If we like the ability to change all of these per mission then we should move the location of the Aero parameters within the data hierarchy under Mission.* from Aircraft.Design.*.
- If we prefer that these variables 'define' and aircraft then Mission.FUEL_FLOW_SCALAR should be removed since that functionality is available on a per-engine basis by setting: Aircraft.Engine.SUBSONIC_FUEL_FLOW_SCALER and Aircraft.Engine.SUPERSONIC_FUEL_FLOW_SCALER.
This Issue should include a full search of the repository for any other variables that need changing in a similar way.
This Issue also requires investigation of how any of these variables may impact GASP based analysis.
Is your feature request related to a problem? Please describe.
No response
Associated Bug Report
No response