You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The next generation autograd is now called jax, and is built by the same guys who built autograd + more, with a somewhat nicer API. One other attractive feature is the ability to JIT compile functions to CPU, GPU and TPU!
As such, I'd like to propose switching over from autograd to jax in requirements.txt. Naturally, this is just a suggestion; I simply thought I'd check out the repo having seen @mattjj star it.
Thank you @ericmjl for your recommendation! I have begun digging deeper into jax and I see it would be beneficial to switch at this initial development stage of MiraPy. 😄 It seems easy to switch from autograd so why not?!
The next generation autograd is now called
jax
, and is built by the same guys who built autograd + more, with a somewhat nicer API. One other attractive feature is the ability to JIT compile functions to CPU, GPU and TPU!As such, I'd like to propose switching over from autograd to jax in
requirements.txt
. Naturally, this is just a suggestion; I simply thought I'd check out the repo having seen @mattjj star it.cc: @mattjj, @dougalm
The text was updated successfully, but these errors were encountered: