Desired capability or behavior.
For FLOPS based analysis Aviary does not calculate HT or VT areas, and these must be specified by the user.
This is ok if you're just copying the design of an existing aircraft, but if redesigning an aircraft or creating a optimizing a new concept this results in incorrect (static) tail sizes.
Suggested implementation.
We have GASP based tail volume coefficients already:
aviary/subsystems/geometry/gaspbased/empennage.py
We should check if the implementation of this is the same for GASP and FLOPS.
If not we should add a FLOPS component.
If the implementation is the same then we should add the GASP subsystem to FLOPS geometry when setting up the Aviary problem for FLOPS based geometry.
https://developer.nasa.gov/AATT-SAI/SandC/blob/main/SandC/FLOPS_Tail_Sizing.py
Desired capability or behavior.
For FLOPS based analysis Aviary does not calculate HT or VT areas, and these must be specified by the user.
This is ok if you're just copying the design of an existing aircraft, but if redesigning an aircraft or creating a optimizing a new concept this results in incorrect (static) tail sizes.
Suggested implementation.
We have GASP based tail volume coefficients already:
aviary/subsystems/geometry/gaspbased/empennage.py
We should check if the implementation of this is the same for GASP and FLOPS.
If not we should add a FLOPS component.
If the implementation is the same then we should add the GASP subsystem to FLOPS geometry when setting up the Aviary problem for FLOPS based geometry.
https://developer.nasa.gov/AATT-SAI/SandC/blob/main/SandC/FLOPS_Tail_Sizing.py