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

Make weight_fn optional in adjacency matrix and fw numpy #158

Merged
merged 13 commits into from
Nov 6, 2020

Conversation

mtreinish
Copy link
Member

@mtreinish mtreinish commented Oct 1, 2020

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:

  • Add tests

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.
@coveralls
Copy link

coveralls commented Oct 1, 2020

Pull Request Test Coverage Report for Build 345500944

  • 16 of 16 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage decreased (-0.02%) to 93.72%

Totals Coverage Status
Change from base Build 345500319: -0.02%
Covered Lines: 2373
Relevant Lines: 2532

💛 - Coveralls

@mtreinish mtreinish removed the on hold label Oct 1, 2020
@mtreinish mtreinish changed the title Make weight_fn optional adjacency matrix fw numpy Make weight_fn optional in adjacency matrix and fw numpy Oct 2, 2020
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.
@mtreinish mtreinish added this to the 0.6.0 milestone Oct 6, 2020
Copy link
Collaborator

@itoko itoko left a 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.

src/lib.rs Outdated Show resolved Hide resolved
@itoko itoko merged commit d8bd470 into Qiskit:master Nov 6, 2020
@mtreinish mtreinish deleted the weight-fn-optional-np branch November 6, 2020 12:35
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 <gaconju@gmail.com>

* Fix Lint

Co-authored-by: Julien Gacon <gaconju@gmail.com>
Co-authored-by: Kevin Krsulich <kevin.krsulich@ibm.com>
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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants