You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Initial values in the input file 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 completely removed 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
The text was updated successfully, but these errors were encountered:
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.
Initial values in the input file 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 completely removed 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
The text was updated successfully, but these errors were encountered: