Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Fixes to various optimization-based control functions#709

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
murrayrm merged 9 commits intopython-control:masterfrommurrayrm:cds112
Mar 19, 2022

Conversation

murrayrm
Copy link
Member

@murrayrmmurrayrm commentedMar 13, 2022
edited
Loading

I recently finished teaching an optimization-based controls course and found a but of small things in the code that needing fixing/improving:

  • Parameters were not being passed properly to differentially flat systems.
  • Basis functions derived fromBasisFamily were not callingBasisFamily.__init__.
  • Changedconstraints keyword inoptimal.solve_ocp andflatsys.point_to_point totrajectory_constraints for more consistency (legacy keyword still works).
  • Initial conditions for simulation of discrete time systems was being passed as a list instead of an ndarray, which caused some odd behavior and wasn't consistent with continuous time system usage.
  • Added check for constraint types in optimal control problem setup (rather than when solving the optimal control problem).
  • Fixed small inconsistency in the way discrete time was handled in setting up an I/O system for model predictive control (should be inherited from system, not passed separately).
  • Unused keywords inOptimalControlProblem now generate an error (mentionedhere).
  • To be consistent with the normal problem formulation, the discrete time optimal cost calculation no longer includes the endpoint (useterminal_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.
  • Added unit tests.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.006%) to 93.601% when pullingf807b33 on murrayrm:cds112 intoe10855e on python-control:master.

@murrayrmmurrayrm added this to the0.9.2 milestoneMar 19, 2022
@murrayrmmurrayrm merged commit4ef15c4 intopython-control:masterMar 19, 2022
@murrayrmmurrayrm deleted the cds112 branchMarch 19, 2022 18:12
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.9.2
Development

Successfully merging this pull request may close these issues.

2 participants
@murrayrm@coveralls

[8]ページ先頭

©2009-2025 Movatter.jp