Skip to main content

Solvers

This package contains all solver implementations and required utility scripts.


Installation

pip install muoblpsolvers

Or use any other package manager.

Alternatively you can install locally (see Development).

C++ python bindings

C++ bindings live in the monorepo subproject bindings/ (muoblpbindings).

Solvers

PuLP name / class module / experiments solver_type / bindings-backed / constructor options:

PuLP name Module solver_type Bindings Options (defaults)
Greedy greedy_solver.py GREEDY no —
Phragmen phragmen.py PHRAGMEN no increasing_scalings=False, kappa=1.0, bos_version=False, eps=1e-6
SummedObjectives summed_objectives_lp_solver.py SUMMING no use_gurobi=False
MethodOfEqualSharesExponential mes/mes_exponential.py MES_EXPONENTIAL no budget_init (required)
MethodOfEqualSharesConstrains mes/mes_constrains.py MES_CONSTRAINT yes cost_modification_base=1.007, max_iterations=200
MethodOfEqualSharesAdd1 mes/mes_add1.py MES_ADD1 yes —
MethodOfEqualSharesUtility mes/mes_utility.py MES_UTILS yes —
SingleTransferableVote single_transferable_vote.py STV yes —
ExpandingApprovals expanding_approvals.py EXPANDING_APPROVALS yes —
SolidCoalitionRefinement solid_coalition_refinement.py SOLID_COALITION_REFINEMENT yes —

Modules are under src/muoblpsolvers/.

Solver contract

All solvers follow PuLP's LpSolver contract:

  • Constructor: Solver(msg=True, timeLimit=None, options=None, **solver_options); solver options are keyword arguments, stored in optionsDict and serialized by toDict()/toJson() (None kwargs are dropped by PuLP).
  • available(): True for pure-python solvers; bindings-backed solvers return whether muoblpbindings imports (imports are lazy, so import muoblpsolvers works without bindings).
  • Status: actualSolve(lp) sets lp.status and returns it.
  • msg=False: no output during solve.
  • timeLimit: Greedy, Phragmen, MES-Exponential and MES-Constrains (coarsely, per iteration) stop early with LpStatusNotSolved; SummedObjectives passes it to CBC/Gurobi; other bindings-backed solvers emit a warning and ignore it.
  • Validation: all PB solvers (all except SummedObjectives) reject programs outside the binary PB shape — no objectives, non 0/1 variables, negative utilities or costs — with PulpSolverError.
  • Known limitation: MES-family, STV, ExpandingApprovals and SolidCoalitionRefinement ignore lower-bound (>=) constraints.

Example Solver

  1. See example SummedObjectivesLpSolver
  2. Solver has to be a class that extends LpSolver
  3. Solver needs to override method actualSolve to accept an instance of MultiObjectiveLpProblem, set lp.status and return it

PuLP registration

import muoblpsolvers registers all 10 solvers into PuLP's registry, so they resolve through the standard PuLP API:

import muoblpsolvers  # side effect: registers solvers
import pulp

solver = pulp.getSolver("Phragmen", kappa=2.0)  # any of the 10 names
"Phragmen" in pulp.listSolvers()                 # True

Registered names: ExpandingApprovals, Greedy, MethodOfEqualSharesAdd1, MethodOfEqualSharesConstrains, MethodOfEqualSharesExponential, MethodOfEqualSharesUtility, Phragmen, SingleTransferableVote, SolidCoalitionRefinement, SummedObjectives.

Mechanism. PuLP 3.3.2 drives getSolver/listSolvers off the module-level list pulp.apis._all_solvers (getSolver builds {cls.name: cls} from it). Registration appends our solver classes to that list in place. It runs automatically on import via register_solvers() (also exported for explicit use); the function is idempotent and only appends classes, so it never instantiates a solver and stays bindings-free (C++ binding imports are lazy, inside each solver's actualSolve).

Development

core and bindings are path dependencies; poetry install compiles bindings from ../bindings (C++20 toolchain, see bindings README).

$ cd multiobjective-lp/solvers # package root
$ poetry install
$ poetry run pytest
$ poetry run pyright
$ poetry run ruff check .. && poetry run ruff format --diff ..  # CI ruff version

Metadata

Release files for muoblpsolvers 0.0.15

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for muoblpsolvers 0.0.15
File Size Uploaded Provenance Actions
muoblpsolvers-0.0.15.tar.gz 14.9 kB With provenance Details for muoblpsolvers-0.0.15.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for muoblpsolvers 0.0.15
File Interpreter ABI Platform Actions
muoblpsolvers-0.0.15-py3-none-any.whl Python 3 none any Details for muoblpsolvers-0.0.15-py3-none-any.whl

Total release size: 36.7 kB

Release files / muoblpsolvers-0.0.15.tar.gz

Download URL muoblpsolvers-0.0.15.tar.gz
Size 14.9 kB
Tags Source
SHA-256 checksum
How to use checksums
8b4bf8c0b65a74b58a5b9fbdf9ffbb0d6f1b5c4d8c32fede47fdf87a4ae1d0ef
BLAKE2b-256 checksum
How to use checksums
1ad560870eeecdb2bf9d3cc1d1276e8d1b7ff852f05eee5508789ad25a9d069c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 13, 2026.

Transparency log

Release files / muoblpsolvers-0.0.15-py3-none-any.whl

Download URL muoblpsolvers-0.0.15-py3-none-any.whl
Size 21.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
958a2f0abdb0efa5bbc62805bc11ee575f2f6035d2a785405e1c27e3550eac71
BLAKE2b-256 checksum
How to use checksums
d8f66fc7cb98cc27acc5508f919d7c52c498e4cdc4afcf8c3fb2fb4f9e8266c4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 13, 2026.

Transparency log

Security for muoblpsolvers 0.0.15

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for muoblpsolvers-0.0.15.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 13, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page