Add FLOPS Tail Sizing Tail Volume Coefficients Subsystem
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 287
- Forks
- 140
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 18
Description
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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading aviary/subsystems/geometry/gaspbased/empennage.py and comparing its tail volume coefficient implementation with FLOPS_Tail_Sizing.py. Trace how FLOPS-based geometry is assembled, then determine whether the existing GASP subsystem can be reused or a FLOPS component is needed. Done means FLOPS analyses calculate tail sizing rather than requiring static HT and VT areas.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100