[WIP] Sinkhorn in log space by rflamary · Pull Request #290 · PythonOT/POT
Types of changes
- Docs change / refactoring / dependency upgrade
- Bug fix (non-breaking change which fixes an issue)
- New feature (non-breaking change which adds functionality)
- Breaking change (fix or feature that would cause existing functionality to change)
Motivation and context / Related issue
We need to implement and use the sinkhorn logsumexp implementation before the backend release; While it is slower in practice it is clearly a better solution when used in differentiable toolboxes such as torch.
How has this been tested (if it applies)
In local scripts + in the numerous new unit tests that have been written for it.
Checklist
- The documentation is up-to-date with the changes I made.
- I have read the CONTRIBUTING document.
- All tests passed, and additional code has been covered with new tests.