Fixes to various optimization-based control functions #709
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I recently finished teaching an optimization-based controls course and found a but of small things in the code that needing fixing/improving:
BasisFamily
were not callingBasisFamily.__init__
.constraints
keyword inoptimal.solve_ocp
andflatsys.point_to_point
totrajectory_constraints
for more consistency (legacy keyword still works).OptimalControlProblem
now generate an error (mentioned here).terminal_cost
instead).create_mpc_iosystem
now re-computes the optimal controller when returning the output, which eliminates an unintended one-step delay in the MPC dynamics.