Skip to content

[Routing] Add support for directed device graphs. #5863

New issue
New issue
Open
Open
[Routing] Add support for directed device graphs.#5863
Assignees
smburdick
Labels
area/devicesarea/routingarea/transformerscomplexity/lowintroduces/modifies 1-2 concepts, should take 1-2 days max for an advanced contributorgood for learningFor beginners in QC, this will help picking up some knowledge. Bit harder than "good first issues"kind/taskA task that's part of a larger efforttriage/acceptedA consensus emerged that this bug report, feature request, or other action should be worked on
Milestone
 
2025-T5: Enhance functions for circuit construction and transformations
@ammareltigani

Description

@ammareltigani
ammareltigani
opened on Sep 7, 2022

Summarize the task
Currently, if a user wants to route their circuit on a device that has asymmetric coupling (i.e. you can execute a CNOT(q1, q2) but not CNOT(q2, q1)) then the transformer raises an error.

Acceptance criteria - when is the task considered done?
As an improvement, we can support directed device graphs using the swap decomposition: SWAP(0,1) <=>
CNOT(0,1), H(0), H(1), CNOT(0,1), H(0), H(1), CNOT(0,1)

Related issues: #5838

Metadata

Metadata

Assignees

Labels

area/devicesarea/routingarea/transformerscomplexity/lowintroduces/modifies 1-2 concepts, should take 1-2 days max for an advanced contributorgood for learningFor beginners in QC, this will help picking up some knowledge. Bit harder than "good first issues"kind/taskA task that's part of a larger efforttriage/acceptedA consensus emerged that this bug report, feature request, or other action should be worked on

Type

No type

Projects

Cirq 2025 roadmap

Status

No status

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions