-
Notifications
You must be signed in to change notification settings - Fork 230
Update to new DPPL version #1636
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Co-authored-by: David Widmann <[email protected]>
|
I'm a bit surprised that we need to overload |
|
Likely yeah, but IMO this should be done in a separate PR? This PR should be "minimal change necessary to make Turing.jl compatible with new DPPL". |
|
Also, it seems like SMC samplers are now broken? o.O Do any of you @yebai @devmotion have any idea as to why this is? I'm not at all familiar with APS so it's a bit difficult to debug. EDIT: Just discovered there's a EDIT 2: Figured it out. |
Sounds good.
Great - I'll take a look at the DPPL PR. |
In the recent breaking release we mistakenly removed the call to `observe(::AbstractSampler, right left, vi)` as a fallback for `DefaultContext`, leading to certain sampler breaking in Turing (TuringLang/Turing.jl#1636). This PR adds back a proper fallback, making overloads such as https://github.com/TuringLang/Turing.jl/blob/tor%2Fdppl-update/src/inference/AdvancedSMC.jl#L353-L356 work as before 0.11.
Codecov Report
@@ Coverage Diff @@
## master #1636 +/- ##
==========================================
+ Coverage 79.32% 79.61% +0.29%
==========================================
Files 23 23
Lines 1422 1413 -9
==========================================
- Hits 1128 1125 -3
+ Misses 294 288 -6
Continue to review full report at Codecov.
|
Pull Request Test Coverage Report for Build 925470820Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
|
Ready with the 👍 once the last test passes? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, just bump the Turing version number? Do we want it to be a breaking release as well?
|
Good quesh. Technically nothing that we export is breaking, buuuut we're exporting |
|
Maybe make it breaking just on the off-chance someone is actually overloading EDIT: I misremebered, |
|
As long as we do not export the methods that were broken in DynamicPPL, technically it is non-breaking. E.g., if we would reexport DynamicPPL or any of these methods it would be clear. It is a bit unclear how to deal with an exported module such as DynamicPPL... But generally if methods are only available internally as |
|
The boundary is blurred further by the fact that most people don't about DPPL but are using stuff from there directly through BUT I was mistaken; we don't have |
This PR makes Turing compatible with [email protected].
EDIT: This should go after #1633 .