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
As for now, we rely on POT and Jax for classical OT and torch for fugw. In order to lighten up the package and ease the maintaining, we should cut out one or more backends.
The text was updated successfully, but these errors were encountered:
I'd be in favor of removing the jax backend. The jit compilation of the sinkhorn kernels is actually slower than running the actual algorithm with POT. Since parcels have almost always different sizes, kernels can't be reused between them. Moreover now that SparseOT is implemented, ott's GPU support is not an advantage anymore.
As for now, we rely on POT and Jax for classical OT and torch for fugw. In order to lighten up the package and ease the maintaining, we should cut out one or more backends.
The text was updated successfully, but these errors were encountered: