Update inference routines #116
Merged
Conversation
This file contains 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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #116 +/- ##
==========================================
+ Coverage 95.17% 95.20% +0.02%
==========================================
Files 17 17
Lines 497 500 +3
==========================================
+ Hits 473 476 +3
Misses 24 24 ☔ View full report in Codecov by Sentry. |
gdalle
changed the title
logL in the inference routines
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.
Warning
Breaking change: bumping version to v0.6.0
forward!,viterbi!andforward_backward!from the public API, rename them with a leading underscore._forward!,_viterbi!and_forward_backward!by passing themkinstead oft1, t2so that they can updatelogLin place. This is breaking because the API of these subfunctions is documented. This change will be useful to tackle Integration with SSMProblems Ecosystem #104.fit!and reactivate the no-allocation tests.