Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Moving from autograd to jax #35

Open
ericmjl opened this issue May 20, 2019 · 1 comment
Open

Moving from autograd to jax #35

ericmjl opened this issue May 20, 2019 · 1 comment
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@ericmjl
Copy link

ericmjl commented May 20, 2019

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

@swapsha96
Copy link
Collaborator

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?!

@swapsha96 swapsha96 added enhancement New feature or request good first issue Good for newcomers labels May 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants