Repository navigation
debug: init windows w/o NaNs at k=-1 if direct=true in MovingHorizonEstimator - #465
Merged
Merged
Conversation
franckgaga
changed the title
De without a NaN if direct==true in MovingHorizonEstimatorDe without a NaN if direct=true in MovingHorizonEstimator
franckgaga
changed the title
De without a NaN if direct=true in MovingHorizonEstimatorNaNs if direct=true in MovingHorizonEstimator
franckgaga
changed the title
NaNs if direct=true in MovingHorizonEstimatorNaNs at start if direct=true in MovingHorizonEstimator
franckgaga
changed the title
NaNs at start if direct=true in MovingHorizonEstimatorNaNs at k=-1 if direct=true in MovingHorizonEstimator
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #465 +/- ##
==========================================
- Coverage 97.22% 97.19% -0.03%
==========================================
Files 28 28
Lines 6874 6879 +5
==========================================
+ Hits 6683 6686 +3
- Misses 191 193 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Member
Author
|
The doc deploy bug is patched in another branch, merging. |
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
2 participants
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.
The$\mathbf{Y_0^m}$ , $\mathbf{U_0}$ , $\mathbf{U_e}$ and $\mathbf{D_e}$ data windows was not correctly initialized if $p=0$ ) just after $k=-1$ according to the table in the extended help of
direct==true(orMovingHorizonEstimatorconstruction. The first element is the time stepMovingHorizonEstimator, which is equal to the operating point by default (can be customized withinitstate!):How to read the table: at$k=0$ we have $N_k=1$ data, thus the first sample is $k-N_k+p = (0) - (1) + (0) = -1$ .
Before this PR it was a
NaNvalue instead of the operating point. Note that this is a minor bugfix since the incorrectNaNvalues vanish once the data windows are filled. Also the bug was not present ifinitstate!was called before the estimations.