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 main reason to use Jax2D over other JAX physics engines such as Brax or MJX is that Jax2D scenes are (largely) dynamically specified. However, Jax2D always has O(n^2) runtime with respect to the number of entities in a scene, since we must always calculate the full collision resolution for every pair of entities. This means it is usually not appropriate for simulating scenes with large numbers (>100) of entities.
In short: Jax2D excels at simulating lots of small and diverse scenes in parallel very fast.
This thread can be used to post more potential alternative solutions to JAX-MD
The text was updated successfully, but these errors were encountered:
Currently we rely on JAX-MD, but the library is not very well maintained, which could become an issue in the future.
Our main requirement is to be able to simulate a large number of entities in parallel (> 10K), which require efficient search of nearest neighbors.
Some potential alternatives recommended by @eleninisioti .
This thread can be used to post more potential alternative solutions to JAX-MD
The text was updated successfully, but these errors were encountered: