package optiml-transport

All checked builds pass
  1. Overview
  2. Docs
Solve optimal transportation problems using the network simplex algorithm

Install 

dune-project
 Dependency

github.com Readme Changelog Edit opam file Versions (1)

Authors

  1. I
    Ilias Garnier

Maintainers

  1. I
    igarnier@protonmail.com

Sources

0.0.1.tar.gz
md5=f9895528430b9ac5fcd685d12b14acab
sha512=39e720b27e08fb7e225aac17919c3964cfe89798983a92e8dea425e742d0a595a1cf9a2e177342f4e8af86c96a7fb8cce30f9ec40254ab32c306805e5bdb9a58

Description

This library provides bindings to the fast optimal transportation library by Nicolas Bonneel, available here: https://perso.liris.cnrs.fr/nicolas.bonneel/FastTransport/ and originally extracted from the LEMON C++ library. Part of the C++ wrapper is copied from https://github.com/PythonOT/POT

Added to opam-repository:

README

optiml-transport - optimal transportation using the network simplex algorithm

These are some bindings to a solver for the optimal transportation problem. The solver uses the network simplex algorithm and is reasonably efficient. The underlying c++ code was obtained through the Python Optimal Transportation toolkit (POT), which itself used some code by Nicolas Bonneel, using some code from the LEMON library.

Dependencies (2)

  1. ocaml >= "4.08"
  2. dune >= "2.8"

Dev Dependencies (1)

  1. odoc with-doc

Optional Dependencies

None

Used by

None

Conflicts

None

Build status

Results of building optiml-transport with each compiler on check.ci.ocaml.org, run of against opam-repository 78c202b. All results for this package.

Each result links to its build log. To keep crawlers from overloading the site, build logs require a GitHub sign-in (see ocurrent/opam-health-check). On your first log, GitHub asks you to “Authorize opam-health-check”, the OCurrent app that runs these checks; it sees only your public profile, not your repositories. The sign-in lasts 30 days.

Version OCaml 4.11 OCaml 4.14 OCaml 5.2 OCaml 5.4 OCaml 5.5
0.0.1 (this version) good good good good good
  • good Package successfully built
  • partial One of the dependencies failed to build
  • bad Package failed to build
  • n/a Package is not available in this environment
  • internal Internal failure