-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
UserWarning: routing_method is not a recognized runtime option when using execute #7200
Comments
At the time the Kwargs in
Kwargs in
@ajavadia: is it your intention that the |
|
Yeah, I'd be in favour of splitting things up to make it clearer as well. At the moment, |
Right, at a certain point we realized that bundling all the arguments for compilation and running into a single function didn't make sense and would result in an ridiculously long function signature and stopped adding explicit kwargs for every field in As for the specific warning message you're seeing emitted, when BackendV1 was added and we had an explicit options field for each backend we made the default passthrough transpile(optimization_level=3)
backend.run(routing_method='sabre', layout_method='sabre') and the warning message is coming from |
This commit switches the default routing and layout method for optimization level 3 to use SabreSwap and Sabre layout passes. The quality of results is typically better with sabre than the default stochastic swap and dense layout we're using now. For optimization level 3 where we try to produce the best quality result and runtime is of secondary concern using sabre makes the most sense (especially after Qiskit#7036 which improves the runtime performance). Also for optimization level 3 currently sabre is typically faster because we increase the number of trials for stochastic swap (which is generally significantly faster) which slows it down as it's doing more work. This should improve the quality and speed of the results in general when running with optimization level 3. In the future we can do more work to improve the runtime performance of the sabre passes and hopefully make it fast enough to use for all the optimization levels which have more constraints on the run time performance than level 3. Related to Qiskit#7112 and Qiskit#7200
* Switch default routing/layout method to sabre for opt level 3 This commit switches the default routing and layout method for optimization level 3 to use SabreSwap and Sabre layout passes. The quality of results is typically better with sabre than the default stochastic swap and dense layout we're using now. For optimization level 3 where we try to produce the best quality result and runtime is of secondary concern using sabre makes the most sense (especially after #7036 which improves the runtime performance). Also for optimization level 3 currently sabre is typically faster because we increase the number of trials for stochastic swap (which is generally significantly faster) which slows it down as it's doing more work. This should improve the quality and speed of the results in general when running with optimization level 3. In the future we can do more work to improve the runtime performance of the sabre passes and hopefully make it fast enough to use for all the optimization levels which have more constraints on the run time performance than level 3. Related to #7112 and #7200 * Clarify punctuation in release note Co-authored-by: Jake Lishman <jake@binhbar.com> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
This is no longer an issue now that |
Information
What is the current behavior?
Calling
raises:
/Users/paul/mambaforge/envs/qiskit/lib/python3.9/site-packages/qiskit/execute_function.py:399: UserWarning: routing_method is not a recognized runtime option and may be ignored by the backend.
However, doing
gives no such error.
Steps to reproduce the problem
What is the expected behavior?
Suggested solutions
The text was updated successfully, but these errors were encountered: