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

Importing jax-moseq produces deprecation error #32

Open
wingillis opened this issue Nov 10, 2023 · 6 comments
Open

Importing jax-moseq produces deprecation error #32

wingillis opened this issue Nov 10, 2023 · 6 comments

Comments

@wingillis
Copy link

wingillis commented Nov 10, 2023

A fresh install of jax-moseq installs jax==0.4.20, which deprecates some classes that chex==0.1.6 depends on, and produces the following error upon import:
AttributeError: module 'jax.interpreters.pxla' has no attribute 'ShardedDeviceArray'

The solution is to update the version of chex to the latest (0.1.84), which no longer references ShardedDeviceArray.

@wingillis wingillis changed the title jax-moseq produces an error on import because chex needs to be updated. Importing jax-moseq produces deprecation error Nov 10, 2023
@calebweinreb
Copy link
Contributor

So are you saying that chex should be pinned to 0.1.84?

@wingillis
Copy link
Author

Yes

@calebweinreb
Copy link
Contributor

I'm a little worried about this given that keypoint-moseq install currently works for most people, and upgrading chex/jax might open a whole can of worms. When you say "a fresh install of jax-moseq installs jax==0.4.20", what do you mean exactly? Like if you update jax-moseq it tries to update jax too?

@bainro
Copy link
Contributor

bainro commented Feb 3, 2024

google-deepmind/chex#251
https://github.com/google-deepmind/chex/tags

Merged to chex master in march, so probably 0.1.8.

I'm having the exact same issue on Ubuntu 22 with GPU. Installing a newer chex gives dependency error from jax-moseq.

@calebweinreb
Copy link
Contributor

Is the dependency error in pip? If so, I think it can just be ignored.

@bainro
Copy link
Contributor

bainro commented Feb 3, 2024

Yeah, just edited my comment as you replied. I did ignore it, thanks Caleb :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants