Allow specification of parameters to test for in kwargs #14
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some AD backends, e.g. ReverseDiff, have a compiled mode which relies on the particular input value provided in the
ADgradient
call. Since we're currently just checking gradient evaluations for the same input values as the one we use for compilation of the tape, we don't catch issues related to this.This PR just makes the input values we run benchmarks on part of the kwargs, with the default values differing from the values present in the
varinfo
we use for compilation.Related discussion: TuringLang/Turing.jl#2091 (comment)
Example from that discussion is now correctly identified to have issues: