We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I already mention this in ReverseDiff's documentation, but I'm opening this issue to increase visibility and track progress.
ReverseDiff has the same perturbation confusion issue as ForwardDiff. My plan to solve this in ReverseDiff is the same as my plan to solve this in ForwardDiff; the tag will be added to the TrackedArray/TrackedReal types (and possibly the tape types, I'm not sure yet).
TrackedArray
TrackedReal
The text was updated successfully, but these errors were encountered:
Here's a simple test case, if anyone is interested:
D(f, x) = ReverseDiff.gradient(x->f(x[1]), [x])[1] D(x -> x * D(y -> x * y, 3), 5) # 3 D(x -> x * D(y -> y * x, 3), 5) # 5
(the correct answer is 2x, or 10).
Sorry, something went wrong.
Hi,
Any luck in fixing this bug?
No branches or pull requests
I already mention this in ReverseDiff's documentation, but I'm opening this issue to increase visibility and track progress.
ReverseDiff has the same perturbation confusion issue as ForwardDiff. My plan to solve this in ReverseDiff is the same as my plan to solve this in ForwardDiff; the tag will be added to the
TrackedArray
/TrackedReal
types (and possibly the tape types, I'm not sure yet).The text was updated successfully, but these errors were encountered: