Please consider lifting custom_vjp
See original GitHub issueAccording to the documentation, there is no flax.custom_vjp
yet. Are there any plans to implement it?
I love the design of flax.vmap
, which adds variable_axes
and split_rngs
. If a similar approach were taken with custom_vjp
, then the ability to lift parameters that I requested https://github.com/google/flax/issues/1712 might be unnecessary.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Tracer seems to leak into vjp through nondiff_argnums #2912
I think this is a bug in how I implemented nondiff_argnums : I made it equivalent to lexical closure, but since custom_vjp functions...
Read more >Custom derivative rules for JAX-transformable Python functions
A related application is to enforce a differentiation convention, perhaps at a boundary. Consider the function ...
Read more >The L.I.F.T. Lounge®️ Delray Beach FL Private Training Studio
VIP Private Training Sessions at The L.I.F.T. Lounge®, located in our brand new studio in Delray Beach, Florida using our patent-pending custom equipment ......
Read more >Lift Tickets - Mountain High Resorts
Ski or Snowboard for just $79 per Day, $39 per Night (5pm-10pm). Please purchase your discounted tickets at the VIP Window at the...
Read more >Ep. #929: Greg Everett on How to Start Olympic Weightlifting ...
I think you're going to enjoy it! Timestamps: 0:00 – Legion VIP One-on-One Coaching: https://www.muscleforlife.show ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
yeah no worries, let us know if it works for you.
Lol I linked the PR to itself instead of to this issue. Thanks for mentioning @levskaya