Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

TSP needs more usage info

Open
#82 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
documentation

Research direction

No file, test, or documentation entry point is named. Start by locating the current TSP usage documentation and reproducing the listed five-node examples, then document supported input ranges, the observed route limitations, and how to set lagrange.

Written by the indexing model from the issue text.

Description

Description
Most TSP problems I try fail to produce a minimal route. The parameters and working range of solvable problems should be outlined.

To Reproduce
The following alternative weights to the 5-node problem, EdgeView([(0, 1), (0, 2), (0, 3), (1, 2), (1, 3), (2, 3)]), all fail:

  • [{'weight': 22.36}, {'weight': 10.0}, {'weight': 14.14}, {'weight': 20.0}, {'weight': 22.36}, {'weight': 22.36}]
    produces route: [3, 1, 0] (non-Hamiltonian route)
  • [{'weight': 2.24}, {'weight': 1.0}, {'weight': 1.41}, {'weight': 2.0}, {'weight': 2.24}, {'weight': 2.24}]
    produces route: [1, 0, 3, 2] (a better answer is [1 2 0 3])
  • [{'weight': 2}, {'weight': 4}, {'weight': 1}, {'weight': 2}, {'weight': 4}, {'weight': 3}]
    produces route: [3, 2, 1, 0] (a better answer is [2 1 0 3])

Expected behavior
More info on range of problem inputs, how to set lagrange, etc

Environment:

  • OS: Windows
  • Python version: 2.7

Additional context
@vgoliber

Dominant language
Python
Stars
94
Forks
62
Avg merge
13h 11m
Merged PRs (30d)
2

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dwavesystems/dwave-graphs

All issues in dwavesystems/dwave-graphs

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.