-
Notifications
You must be signed in to change notification settings - Fork 164
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
Make weight_fn optional in adjacency matrix and fw numpy #158
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit makes the weight_fn argument for graph_adjacency_matrix, digraph_adjacency_matrix, graph_floyd_warshall_numpy, and digraph_floyd_warshall_numpy optional. A new kwarg is added default_weight (which defaults to 1.0) which can be used instead of passing a callable. If weight_fn is not set the value of default_weight will be used for all edges. Previously, a function returning a fixed value would have to be used to accomplish this. In practice there was not much overhead to just using something like 'lambda _: 1' as the weight fn, but it was a bit of a clumsy interface.
Pull Request Test Coverage Report for Build 345500944
💛 - Coveralls |
mtreinish
added a commit
to mtreinish/qiskit-core
that referenced
this pull request
Oct 5, 2020
This commit migrates Terra's CouplingMap class to us retworkx internally instead of networkx providing >10x speed improvement for CouplingMap operations. Requires: Qiskit/rustworkx#157 Qiskit/rustworkx#156 Qiskit/rustworkx#144 Qiskit/rustworkx#143 Qiskit/rustworkx#147 Qiskit/rustworkx#158 Qiskit/rustworkx#162 Qiskit/rustworkx#161 all be applied to the retworkx version installed.
9 tasks
itoko
reviewed
Nov 4, 2020
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Just one nit pick.
itoko
approved these changes
Nov 6, 2020
mergify bot
added a commit
to Qiskit/qiskit
that referenced
this pull request
Dec 4, 2020
* WIP: Use retworkx for CouplingMap This commit migrates Terra's CouplingMap class to us retworkx internally instead of networkx providing >10x speed improvement for CouplingMap operations. Requires: Qiskit/rustworkx#157 Qiskit/rustworkx#156 Qiskit/rustworkx#144 Qiskit/rustworkx#143 Qiskit/rustworkx#147 Qiskit/rustworkx#158 Qiskit/rustworkx#162 Qiskit/rustworkx#161 all be applied to the retworkx version installed. * DNM: Install retworkx from source * DNM: Add retworkx custom branch to travis * Fix draw() copy paste error * Fix typo * DNK: Add source retworkx to docs build * Fix lint * Use graph_distance_matrix instead of floyd warshall * DNM also add retworkx from source for image test job * Use Gnm random function from retworkx in token swapper tests * Remove nx import from token swapper tests * Fix lint * Remove install from git from CI config since retworkx 0.6.0 is released * Fix api call * Use retworkx generators where possible for constructors * Remvoe source install from travis config * Bump version in setup.py too * Use extend_from_edge_list for from_full * Update qiskit/transpiler/coupling.py * Use edge_list() return and has_edge() in sabre In Qiskit/rustworkx#204 the return type of the edge_list() method will be returned as a custom sequence type the defer the type conversion from rust to python. So casting to a list no longer will be a no-op after that point so this commit removes the cast. At the same time in the sabre swap pass one of the bottlenecks at large qubit counts is traversing that edge list looking for edges, this updates that to use the has_edge() method which should be faster than a full list traversal every iteration. * Fix issue in layout_transformation pass In #5281 the layout transformation pass was updated to handle the case where the coupling map was not defined. In those cases for the purposes of the layout transformation it treats the coupling map as being fully connected. So it creates a new full coupling map to use for the token swapper. However, it neglects that the token swapper expects an undirected graph and was passing in a directed graph. This didn't matter too much for the networkx based coupling map object because networkx can handle directed or undirected in the same function. But, for retworkx directed graphs and undirected graphs are different types an can't be used interchangeably. This commit fixes this issue in that pass. * Update qiskit/transpiler/passes/routing/algorithms/token_swapper.py Co-authored-by: Julien Gacon <[email protected]> * Fix Lint Co-authored-by: Julien Gacon <[email protected]> Co-authored-by: Kevin Krsulich <[email protected]> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit makes the weight_fn argument for graph_adjacency_matrix,
digraph_adjacency_matrix, graph_floyd_warshall_numpy, and
digraph_floyd_warshall_numpy optional. A new kwarg is added
default_weight (which defaults to 1.0) which can be used instead of
passing a callable. If weight_fn is not set the value of default_weight
will be used for all edges. Previously, a function returning a fixed
value would have to be used to accomplish this. In practice there was
not much overhead to just using something like 'lambda _: 1' as the
weight fn, but it was a bit of a clumsy interface.
TODO: