forward-mode differentiation of lax.scan suddenly not working
See original GitHub issueWhen running a piece of code that was working earlier today, I am suddenly getting the following error
NotImplementedError: Forward-mode differentiation rule for 'while' not implemented
If necessary I can try to create a minimal repo, but I will say that if I replace a lax.scan call with a for loop then this error goes away.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
jax.lax.scan - JAX documentation - Read the Docs
Scan a function over leading array axes while carrying along state. ... must hold a fixed shape and dtype across all iterations (and...
Read more >BIG-IP 16.0.0 Fixes and Known Issues - AskF5 - F5 Networks
Cumulative fix details for BIG-IP v16.0.0 that are included in this release. 919465 : A dwbld core on configuration changes on IP Intelligence...
Read more >Database Engine events and errors - SQL Server
Consult this MSSQL error code list to find explanations for error messages for SQL Server database engine events.
Read more >Rewriting for loop with jax.lax.scan - python - Stack Overflow
I'm having troubles understanding the JAX documentation. Can somebody give me a hint on how to rewrite simple code like this with jax.lax.scan...
Read more >PRO-1150HD PRO-950HD - Pioneer Electronics
Sudden stops, excessive force and uneven floor surface can cause the product ... The remote control unit may not work properly if the...
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 Free
Top 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
Whooo!!! As always, what a herculean effort Matt!!
I think I introduced the real issue in #1224, because in these lines I’m effectively creating JVPTracers (with zeros) for integer-valued arguments. I think Dougal had some clever way of avoiding that before, and I clobbered it!