-
Notifications
You must be signed in to change notification settings - Fork 36
Zygote support - workaround setproperty! and getproperty #31
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
Maybe one could use |
Sounds good. |
I guess the same applies to TuringLang/Turing.jl#783 🙂 |
I still think it's good to use |
It seems the tests are copied from Turing's implementation, so my comments/questions here are the same as in the Turing PR. |
Just a general question: It seems some files in test/* copied from Turing. Are they modified in any way? Otherwise, wouldn't it be possible to run downstream tests by calling/executing the corresponding test files in Turing and just add Turing as a test dependency? |
It's less than ideal but see #18 for more details. |
Codecov Report
@@ Coverage Diff @@
## master #31 +/- ##
==========================================
- Coverage 88.88% 88.85% -0.04%
==========================================
Files 9 9
Lines 729 727 -2
==========================================
- Hits 648 646 -2
Misses 81 81
Continue to review full report at Codecov.
|
Yeah, we experienced similar problems in JuliaDiffEq with, e.g., breaking changes in DiffEqBase that affected OrdinaryDiffEq or changes in OrdinaryDiffEq that broke DelayDiffEq. |
@devmotion any objections to merging this once tests pass? |
No, LGTM. |
This PR makes DynamicPPL compatible with Zygote by avoiding custom
setproperty!
andgetproperty
forvi::VarInfo
. Zygote errors when using the custom definitions that we had.