-
Notifications
You must be signed in to change notification settings - Fork 97
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
Include Op in message when raising NotImplementedError from grad #711
Comments
hello! i'll take up this issue. i understand the issue and also saw the main issue on pymc. how should i start solving this? |
You should tweak this base case NotImplementedError, to include Line 360 in 090b844
|
Im trying to use the |
i made some commits to my fork but they arent showing up in this issue for u to review? 😕 |
You need to open a pull request from your fork: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork |
Description
When grad fails because a specific Op doesn't support it it's quite difficult to figure out which one it was without jumping on an interactive debugger
https://discourse.pymc.io/t/avoiding-non-nuts-samplers-when-broadcasting-a-multiplication-operation/14245/4?u=ricardov94
We should return something like
NotImplementedError(f"grad not implemented for Op {self}")
in a base class.Or use the
grad_not_implemented
functionality that exists for partial grad implementations which also provides a more readable error IIRCThe text was updated successfully, but these errors were encountered: