-
Notifications
You must be signed in to change notification settings - Fork 219
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
Precompilation fails while using ReverseDiff backend #1400
Comments
As explained on Slack, On the other hand |
Hi @devmotion
But I still get a similar error with |
Ah nice, so it seems my hypothesis was correct and the precompilation problem is caused by Requires. The error messages that you get now with your Turing fork without Requires are caused by AdvancedVI - and there exactly the same problem exists: the ReverseDiff support is optional, hidden in a |
Thank you @devmotion. I will make the corresponding changes. |
ReverseDiff will support ChainRules (but it is not clear yet when) (which BTW should also be used to implement custom adjoints for Zygote - we need ZygoteRules though since we want to get the Zygote-specific pullback here). Maybe together with something like #1402 that would allow use to remove any optional dependencies for AD. It seems ReverseDiff and in particular Memoization wouldn't pull in too many additional dependencies though. So the main question would be how much these additional dependencies would increase loading times I guess. |
Can this be closed? |
yes @trappmartin I think this can be closed. If anyone wants to precompile with |
@trappmartin can this be added to Autodiff page as a note at the end of switch-ad modes block? custom packages using reversediff with rdcache won't be precompiled because Reversediff and Memoization are an optional dependency to Turing.jl and AdvancedVI.jl refer issue #1400 of Turing and JuliaLang/Pkg.jl#1285 (comment) |
Likely fixed by #1877 |
I have created an MWE here. The description is in README.md of the repository.
This reply in the slack thread might be relevant
The text was updated successfully, but these errors were encountered: