JuliaDiff / JuliaDiff/ChainRulesTestUtils.jl
nograd tests
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 50
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/JuliaDiff/ChainRules.jl/pull/223 manually implements a nograd. Once someone has gotten around to sorting https://github.com/JuliaDiff/ChainRulesCore.jl/issues/150 we'll be able to nograd loads of things really easily, at which point it starts to make sense to want to have a simple way to test that things have been successfully nograd-ed and regressions don't happen.
The tests I had to implement in https://github.com/JuliaDiff/ChainRules.jl/pull/223 are quite verbose and boilerplate-y, so it would be good to have a one-liner that covers both frules and rrules.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading ChainRules.jl PR #223 and ChainRulesCore.jl issue #150, then inspect the verbose nograd tests described there. Define a concise test utility that covers both frules and rrules, and verify that it detects regressions when functions expected to be nograd-ed are no longer so.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100