-
Notifications
You must be signed in to change notification settings - Fork 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
Diffractor as backend for Turing? #240
Comments
I think it should be feasible. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, this is more a naive question than an issue so apologies if posted at the wrong place.
I asked on Turing whether they had any plans/interest in supporting Diffractor as a backend, and they mentioned it would in-principle be feasible. I was just wondering if Diffractor could be an interesting option for Turing (with expected speedups, especially in the problematically slow areas of current existing AD backends)? And if so whether there were any long-term plans to work towards this integration, or whether Diffractor was made with different goals in mind than Bayesian sampling. Thanks for the hard work!
The text was updated successfully, but these errors were encountered: