Skip to main content

PyLKH

This is a super simple Python wrapper for the constrained traveling salesman and vehicle routing problem solver called LKH-3.

If you want to use this wrapper, you need to install LKH-3 first. For example, on Ubuntu:

wget http://akira.ruc.dk/~keld/research/LKH-3/LKH-3.0.6.tgz
tar xvfz LKH-3.0.6.tgz
cd LKH-3.0.6
make
sudo cp LKH /usr/local/bin

LKH-3 expects problems in the TSPLIB format. It extends the format to support VRPs.

Using PyLKH you can solve problems represented as Python objects or files.

CAUTION: distances are represented by integer values in the TSPLIB format. This can produce unexpected behaviour for some problems, like those with all nodes within the unit square. You can use the EXACT_2D distance to avoid rounding issues.

Install

pip install lkh

Example

import requests
import lkh

problem_str = requests.get('http://vrp.atd-lab.inf.puc-rio.br/media/com_vrp/instances/A/A-n32-k5.vrp').text
problem = lkh.LKHProblem.parse(problem_str)

solver_path = '../LKH-3.0.6/LKH'
lkh.solve(solver_path, problem=problem, max_trials=10000, runs=10)

Output (values correspond to nodes, which are 1-indexed, not node indicies, which are 0-indexed):

[[27, 8, 14, 18, 20, 32, 22],
 [25, 28],
 [15, 29, 12, 5, 24, 4, 3, 7],
 [30, 19, 9, 10, 23, 16, 11, 26, 6, 21],
 [13, 2, 17, 31]]

API

lkh.solve(solver='LKH', problem=None, problem_file=None, **kwargs)

Solve a problem instance.

Parameters

  • solver (optional): Path to LKH-3 executable. Defaults to LKH.

  • problem (optional): Problem object. LKHProblem is preferred but tsplib95.models.StandardProblem also works. problem or problem_file is required.

  • problem_file (optional): Path to TSPLIB-formatted problem. problem or problem_file is required.

  • kwargs (optional): Any LKH-3 parameter described here (pg. 5-7) or here (pg. 6-8). Lowercase works. For example: runs=10.

Returns

routes: List of lists of nodes (nodes, not node indicies).

class lkh.LKHProblem

A problem that can be solved by LKH-3. Fields are (partially) described here (pg. 4-6). Inherits from tsplib95.models.StandardProblem.

The available specification fields are:

  • CAPACITY
  • COMMENT
  • DEMAND_DIMENSION
  • DIMENSION
  • DISPLAY_DATA_TYPE
  • DISTANCE
  • EDGE_DATA_FORMAT
  • EDGE_WEIGHT_FORMAT
  • EDGE_WEIGHT_TYPE
  • NAME
  • NODE_COORD_TYPE
  • RISK_THRESHOLD
  • SALESMEN
  • SCALE
  • SERVICE_TIME
  • TYPE
  • VEHICLES

The available data fields are:

  • BACKHAUL_SECTION
  • CTSP_SET_SECTION
  • DEMAND_SECTION
  • DEPOT_SECTION
  • DISPLAY_DATA_SECTION
  • DRAFT_LIMIT_SECTION
  • EDGE_DATA_SECTION
  • EDGE_WEIGHT_SECTION
  • FIXED_EDGES_SECTION
  • NODE_COORD_SECTION
  • PICKUP_AND_DELIVERY_SECTION
  • REQUIRED_NODES_SECTION
  • SERVICE_TIME_SECTION
  • TIME_WINDOW_SECTION

You probably want to initialize a problem instance using one of the following class methods:

classmethod load(filepath, **options)

Load a problem instance from a text file.

Inherited from tsplib95.problems.Problem.load.

classmethod parse(text, **options)

Parse text into a problem instance.

Inherited from tsplib95.problems.Problem.parse.

classmethod read(fp, **options)

Read a problem instance from a file-like object.

Inherited from tsplib95.problems.Problem.read.

Metadata

Release files for lkh 2.0.0

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

Built distribution (wheel)

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

Release files / lkh-2.0.0-py3-none-any.whl

Download URL lkh-2.0.0-py3-none-any.whl
Size 24.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4f0086b18f616afe46c67cf1acfbfbae5c3dc57c54fe49fab482a034782efb9b
BLAKE2b-256 checksum
How to use checksums
c673bc14b1c26703919425035a6c024d7014fd0a8a2b581f61b83bf2136bcae8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/4.0.2 CPython/3.10.12

Security for lkh 2.0.0

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

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