[feat] Expose filtered edgelist based on coupler type
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- backend-api-design
Research direction
Start by locating DWaveSampler and the qpu.edgelist entry point, then check whether coupler-type classification already exists. Compare an odd_coupler_edgelist attribute with the proposed recognise_coupler_type function, and validate that the result filters odd, internal, and external couplers as intended.
Written by the indexing model from the issue text.
Description
Current Problem
I would like to iterate over all the odd couplers, internal and external couplers, while creating a problem.
It would be convenient if there is a DWaveSampler attribute that could return this.
Proposed Solution
Similar to qpu.edgelist where qpu is a DWaveSampler, it would be convenient to have qpu.odd_coupler_edgelist or some other solution that could filter the qpu.edgelist to only the ones with odd couplers. Im not sure if something like this already exists.
Alternatives Considered
Create a function recognise_coupler_type(q0 : int, q1 : int) -> CouplerType that does the classification and use this to filter the qpu.edge_list as needed.
This issue was moved from https://github.com/dwavesystems/dwave-ocean-sdk/issues/340
- 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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dwavesystems/dwave-graphs
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
dwavesystems/dwave-graphs#232 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
dwavesystems/dwave-graphs#260 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
dwavesystems/dwave-graphs#258 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 52/100
dwavesystems/dwave-graphs#256 ·
-
bug/fix
Difficulty 3/5 1-2 days Newbie friendliness 35/100
dwavesystems/dwave-graphs#255 · 8 comments ·
All issues in dwavesystems/dwave-graphs
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Arekkazu/sgpmp-backend#744 ·
Maintainers usually reply within 1 day
-
agent/reviewer
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
projectbluefin/utah-packages#634 ·
Maintainers usually reply within 1 day
-
enhancement good first issue help wanted
Difficulty 2/5 1-2 days Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
home-assistant/core#188613 ·
Maintainers usually reply within 1 day
-
WebsiteOpengood first issue
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
TanbirRamim/open-source-radar#314 ·
Maintainers usually reply within 1 day