Jumpy 1.0 is now live, and the project is stable and mature.

Jumpy is a lightweight project for easily switching between Jax and Numpy functions that can serve as a drop-in replacement for Jax. This allows for writing one codebase that can use either backend, allowing for creating codebases that work with either data structure type or easier debugging of code. This project is already being used in Gymnasium to create environment wrappers that can support both Numpy and Jax-based hardware accelerated environments. We plan to continue improving the project with support for PyTorch functions, all Numpy functions and more functionality to support enabling or disabling different backends

You can read the full release notes here: https://github.com/Farama-Foundation/Jumpy/releases/tag/1.0.0

Comments

You must log in or register to comment.

dats_ah_numba_wang t1_jcl7k6w wrote on March 17, 2023 at 5:11 PM

#2,254,988

Didnt know i needed this.

limpbizkit4prez t1_jclabza wrote on March 17, 2023 at 5:29 PM

#2,255,139

What's value in using this instead of "jax.numpy as np"?

r_linux_mod_isahoe t1_jclc6rp wrote on March 17, 2023 at 5:41 PM

#2,255,244

Replying to limpbizkit4prez (#2,255,139)

porting an existing codebase to jax? Using any existing algorithm that's implemented in numpy but on jax backend? The opportunities are massive

limpbizkit4prez t1_jcld70o wrote on March 17, 2023 at 5:47 PM

#2,255,314

Replying to r_linux_mod_isahoe (#2,255,244)

Yeah, but if I have a code base written in numpy and want to use jax, wouldn't I need to do the same amount of refactoring to integrate this as I would with regular jax? Are there a lot of functions in numpy that don't exist in jax.numpy?

LappenX t1_jcln1pc wrote on March 17, 2023 at 6:51 PM

#2,255,874

You don't want to use jax without jit.

jkterry1 OP t1_jcm0qqj wrote on March 17, 2023 at 8:20 PM

#2,256,621

Replying to LappenX (#2,255,874)

What do you mean? This allows you do use it if you want