-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
If you see this error, please let us know by opening an issue #2346
Comments
This issue would be fine! But we’ll definitely need more detail, ideally with a minimal example to reproduce the issue and a stack trace. |
Hi @shoyer, I've done my best to rip the code from our The context of the error comes from trying to use autodiff in order to differentiate through a minimisation by gradient descent. The current way we do that in practice makes use of this implementation of Christianson's two-phase solver for fixed point differentiation. We were trying to speed things up by calling As one may expect, this error is invariant to the details of the problem we were trying to solve, so the code example below just uses a dummy likelihood that returns 1.
I have a feeling this probably concerns details of the Hope this helps! :) |
And here's the long stack trace:
|
Very possibly unrelated but we've run into this error while writing We haven't really encountered it since so I'm not sure what would cause this without diving deep into |
Sorry for the slow response. The only place we've ever seen this error arise is in using I think #2026 fixes this: in fact, coincidentally (because I hadn't looked at this issue in detail until just now), in the tutorial notebook added by that PR, I included a reverse-mode differentiable |
I just merged #2026, so I believe this issue with custom_transforms is fixed (almost tautologically). Please take a look at the tutorial notebook for the new way to define custom JVPs / VJPs. I'm going to close this specific issue but please open new ones as questions about the new API arise. I can also help update old custom_transforms code if needed. |
That is correct! That is essentially how it is done in I'm super excited to see that it supports |
in our code over at https://github.com/pyhf/neos we run into an issue when jit'ing functions that report
we did manage to reach it, what would be the best way to report more detail?
cc @phinate
The text was updated successfully, but these errors were encountered: