fixed fixed_lag_smoothing#1261
Closed
shengmincui wants to merge 3 commits into
Closed
Conversation
Collaborator
|
Thanks @shengmincui. This PR is a very large dump (+153k lines across 39 renamed chapter notebooks) rather than a focused fix to fixed_lag_smoothing, so it can't be reviewed or merged as-is. If fixed_lag_smoothing needs a fix, please open a small focused PR touching just probability.py. Thanks! |
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.
I found that the fixed_lag_smoothing() function in the code probability.py does not implement the persistence of the arguments. We wrote the fixed lag smoothing algorithm as a class and implemented the persistence of f, B, and t.