Skip to content
This repository has been archived by the owner on Aug 14, 2024. It is now read-only.

Double check overhead computation for t|ket> mapper #7

Open
boschmitt opened this issue May 5, 2022 · 0 comments
Open

Double check overhead computation for t|ket> mapper #7

boschmitt opened this issue May 5, 2022 · 0 comments

Comments

@boschmitt
Copy link
Collaborator

IIRC, t|ket> mapper is not exclusively SWAP-based, i.e., it might choose to
add CNOTs directly (bridges). If that is the case, we need to double check that
we are calculating the overhead correctly for the case we use the vanilla
mapper.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant