Better initial guessing
@cmbenne3 is already working on this.
Since Feb 20, 2026.
- Dominant language
- Python
- Stars
- 287
- Forks
- 140
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 18
Description
Desired capability or behavior.
Initial guessing is currently provided through the input file. This initial guessing is generated by input file conversion or must be provided by the user, and these values are designed for use with 2DOF missions. Initial guessing should be computed at runtime after loading the aircraft to keep it up-to-date with any changes to the input file, and only values relevant to the mission analysis method being used should be calculated.
The ability for users to specify initial values should still be supported, and should overwrite computed values so users can provide "better" guesses if they want. Creating initial values upon input file conversion should be removed in favor of doing it at runtime instead. The way initial guesses are created should be given a closer look for ways to make it more robust to various configurations (hybrid/all-electric, etc.) and improve its accuracy. Initial guessing may eventually be able to be optional once shooting is introduced (get initial guesses for collocation from a shooting run).
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.