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

Chimera and Pegasus generators don't allow for Chimera/Pegasus indices when node/edge lists are passed in

Open
  • Is something wrong?
#170 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
python
Domain
data

Research direction

Start by reproducing the two chimera_graph() calls in the issue, then compare the corresponding behavior of pegasus_graph() when coordinates=True and node or edge lists are supplied. Done means both generators use Chimera/Pegasus index labels consistently with and without explicit node and edge lists.

Written by the indexing model from the issue text.

Description

Description
chimera_graph() and pegasus_graph() have a parameter 'coordinates' that, if true, should mean that the node labels are 4-tuple chimera/pegasus indices. If false, they'll be linear integer indices.

This is currently not true when the user passes in node and edge lists (the node labels remain as linear integers even when coordinates=True). This seems like unwanted behaviour.

To Reproduce
The following two snippets will result in different indexing schemes.

            G = dnx.chimera_graph(*shape, 
                                  node_list=nodelist, 
                                  edge_list=edgelist,
                                  coordinates=True)

            G = dnx.chimera_graph(*shape, 
                                  coordinates=True)

Additional context
May want to also consider this adjacent issue: https://github.com/dwavesystems/dwave-system/issues/289

Dominant language
Python
Stars
95
Forks
62
Avg merge
8h 49m
Merged PRs (30d)
3

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.