Skip to content

Creating a challenging backend to show the transpiler stochasticity #12116

Merged
jakelishman merged 1 commit into
Qiskit:mainfrom
1ucian0:doc/transpiler/1
Apr 4, 2024
Merged

Creating a challenging backend to show the transpiler stochasticity #12116
jakelishman merged 1 commit into
Qiskit:mainfrom
1ucian0:doc/transpiler/1

Conversation

@1ucian0
Copy link
Copy Markdown
Member

@1ucian0 1ucian0 commented Apr 2, 2024

The documentation about the transpiler shows that the process is stochastic in https://docs.quantum.ibm.com/api/qiskit/transpiler#routing-stage:

In order to highlight this, we run a GHZ circuit 100 times, using a “bad” (disconnected) initial_layout:
image
image
This distribution is quite wide, signaling the difficulty the swap mapper is having in computing the best mapping.

Which is not very wide. That's because GenericFakeBackend replaced a FakeBackend in #11376. The GenericFakeBackend has an all-to-all connectivity by default.

This PR produces the following image:
image

@1ucian0 1ucian0 added documentation Something is not clear or an error documentation Changelog: None Do not include in the GitHub Release changelog. labels Apr 2, 2024
@1ucian0 1ucian0 requested a review from a team as a code owner April 2, 2024 11:41
@qiskit-bot
Copy link
Copy Markdown
Collaborator

One or more of the the following people are requested to review this:

  • @Qiskit/terra-core

@coveralls
Copy link
Copy Markdown

Pull Request Test Coverage Report for Build 8522176991

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • 2 unchanged lines in 1 file lost coverage.
  • Overall coverage increased (+0.003%) to 89.341%

Files with Coverage Reduction New Missed Lines %
crates/qasm2/src/lex.rs 2 92.37%
Totals Coverage Status
Change from base Build 8521949858: 0.003%
Covered Lines: 60257
Relevant Lines: 67446

💛 - Coveralls

Copy link
Copy Markdown
Member

@jakelishman jakelishman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems like a logical improvement to the docs to me - thanks for fixing it!

@jakelishman jakelishman added the stable backport potential Make Mergify open a backport PR to the most recent stable branch on merge. label Apr 4, 2024
@jakelishman jakelishman added this to the 1.0.3 milestone Apr 4, 2024
@jakelishman jakelishman added this pull request to the merge queue Apr 4, 2024
Merged via the queue into Qiskit:main with commit 59bdff9 Apr 4, 2024
mergify Bot pushed a commit that referenced this pull request Apr 4, 2024
github-merge-queue Bot pushed a commit that referenced this pull request Apr 4, 2024
(cherry picked from commit 59bdff9)

Co-authored-by: Luciano Bello <bel@zurich.ibm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Changelog: None Do not include in the GitHub Release changelog. documentation Something is not clear or an error documentation stable backport potential Make Mergify open a backport PR to the most recent stable branch on merge.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants