added: call gc with NaN values at boundaries in MovingHorizonEstimator construction#364
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #364 +/- ##
=======================================
Coverage 98.56% 98.56%
=======================================
Files 27 27
Lines 5418 5431 +13
=======================================
+ Hits 5340 5353 +13
Misses 78 78 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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.
It should help the user for debugging the implementation of the custom nonlinear inequality constraint function$\mathbf{g_c}$ in the
MovingHorizonEstimator.The function is tested with the growing windows (as it was already the case), and with the "correct"
NaNvalues at the boundaries (the new feature), following the documentation in the extended help. A@warnis printed if there is any non-finite numbers in theLHSvector.I also verify for any non-finite numbers in the equivalent feature of
NonLinMPC.