Performance/Constraints subsystem
Open
@jkirk5 is already working on this.
Since Aug 25, 2025.
epic
- Dominant language
- Python
- Stars
- 287
- Forks
- 140
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 18
Description
Desired capability or behavior.
Aviary needs a performance constraints subsystem (name TBD) that runs after each aircraft sizing iteration to determine various performance values that might be constraints on aircraft design. This could include but is not limited to field lengths, maneuvers, and other criteria. FLOPS has a list of examples of performance constraints that can be applied to an aircraft, as an example starting point.
Is your feature request related to a problem? Please describe.
No response
Associated Bug Report
No response
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.
Assessment
This issue has not been assessed yet.