Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set max_trials for VF2Layout in preset pass managers. (backport #10054) #10061

Merged
merged 1 commit into from
May 2, 2023

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented May 2, 2023

This is an automatic backport of pull request #10054 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

* Set max_trials for VF2Layout in preset pass managers.

By setting max_trials, we limit the number of layouts
enumerated and scored when iterating through vf2_mapping().

This is necessary for scoring to complete in a reasonable
amount of time for circuits with many connected components
on larger (e.g. 400 qubit) devices.

These limits were chosen using a fake 400 qubit device,
using 200 connected components, where each component is
a single CX gate.

Because layout scoring scales linearly
with the number of qubits in the circuit, 250,000 (O3)
takes abount a minute, 25,000 (O2) takes about 6 seconds,
and 2,500 (O1) takes less than a second.

* Address review comments.

* Return tuple of None instead for finer control and a better interface.

* Add deprecation notice to release note.

* Remove deprecation until 0.25.0.

* Remove unused import.

(cherry picked from commit f13b1ed)
@mergify mergify bot requested a review from a team as a code owner May 2, 2023 18:11
@qiskit-bot
Copy link
Collaborator

Thank you for opening a new pull request.

Before your PR can be merged it will first need to pass continuous integration tests and be reviewed. Sometimes the review process can be slow, so please be patient.

While you're waiting, please feel free to review other open PRs. While only a subset of people are authorized to approve pull requests for merging, everyone is encouraged to review open pull requests. Doing reviews helps reduce the burden on the core team and helps make the project's code better for everyone.

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

  • @Qiskit/terra-core

@mtreinish mtreinish enabled auto-merge May 2, 2023 18:15
@mtreinish mtreinish added the Changelog: Bugfix Include in the "Fixed" section of the changelog label May 2, 2023
@mtreinish mtreinish added this to the 0.24.0 milestone May 2, 2023
@mtreinish mtreinish added this pull request to the merge queue May 2, 2023
Merged via the queue into stable/0.24 with commit daebee5 May 2, 2023
@mergify mergify bot deleted the mergify/bp/stable/0.24/pr-10054 branch May 2, 2023 21:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Changelog: Bugfix Include in the "Fixed" section of the changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants