added: lastu keyword argument to moveinput!#274
Merged
Merged
Conversation
It's default is to recuperate the value automatically stored in `mpc.lastu0`.
lastu argument to moveinput!lastu keyword argument to moveinput!
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #274 +/- ##
=======================================
Coverage 98.45% 98.45%
=======================================
Files 28 28
Lines 4657 4659 +2
=======================================
+ Hits 4585 4587 +2
Misses 72 72 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Benchmark Results (Julia v1)Time benchmarks
Memory benchmarks
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Its default value is to recuperate the value automatically stored at
mpc.lastu0, or more precisely:to avoid wasteful allocations in handling the operating point. I think it's cleaner this way since:
moveinput!docstring. It was a bit too much implicit before this PR.This PR is inspired by LinearMPC.jl API, see darnstrom/LinearMPC.jl#27.