-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Autotuner #21
base: main
Are you sure you want to change the base?
Autotuner #21
Conversation
…imizerstate into functions.
…ht/rosplane into 10-autotune-for-rosplane
…th current point not being a numpy array.
… acccount for working with jacobian, at bracketing with bugfixing.
…ther options we want to change based on the gains, we can add them there as well.
I also don't know if I'm going to have time to finish this. The approach we were using before of a gradient based optimization is a flawed approach I think, as it requires too many step iterations to converge. A system identification type method would be better. However, much of the work we did here was simply creating the functionality we needed to have the autopilot perform an automated sequence to measure the system response. That portion of this work would probably still be useful for a system identification type approach. |
An autotuner for ROSplane would make it much easier for people to use, so this is a gradient-based optimization approach for an autotuner.