Repository navigation
Error/Difference in semantics in jax.shard_map #35463
Unanswered
wittenator
asked this question in
Q&A
Replies: 1 comment
|
Hi! I looked into this a bit and looks like a diffrax bug to me. With check_vma=True, I get: This should indeed be fixed by diffrax/equinox. With check_vma=False, I get the same |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
This ticket patrick-kidger/diffrax#735 shows an VMA error in a jax.shard_map with a jax.scan call that can be mitigated by setting check_vma=False. Interestingly, while passing the mesh to the shard_map and setting check_vma=False works for the example, automatically inferring the mesh and unsetting the VMA check fails with the following error:
As pointed out in patrick-kidger/diffrax#738 this may actually be a bug in Jax, but since I cannot reproduce it yet without diffrax I would like to open a discussion first. The stack trace looks as follows:
All reactions