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

Initialize Lattices with networkx.Graphs #465

Closed
Cryoris opened this issue Dec 17, 2021 · 2 comments · Fixed by #472
Closed

Initialize Lattices with networkx.Graphs #465

Cryoris opened this issue Dec 17, 2021 · 2 comments · Fixed by #472
Assignees
Labels
type: feature request New feature or request

Comments

@Cryoris
Copy link
Contributor

Cryoris commented Dec 17, 2021

What should we add?

It would be nice to allow the initialization on Lattices not only with retworkx graphs but also with networks graphs. Networkx, to date, still has a lot more features and pre-defined graphs that users have access to, and is probably the standard graph library in Python.

@Cryoris Cryoris added the type: feature request New feature or request label Dec 17, 2021
@Cryoris Cryoris self-assigned this Dec 17, 2021
@mtreinish
Copy link
Collaborator

I agree with everything in this issue, I would appreciate issues being opened on retworkx when you encounter a feature gap. Mainly because we'd like retworkx to be usable everywhere and we can prioritize features needed for a real use case. It's hard to know which functionality to prioritize without requests from users.

As an aside the current dev branch has a bunch of new graph generators, you can see the list here: https://qiskit.org/documentation/retworkx/dev/api.html#generators although I don't think any are really applicable to lattices. @k-tamuraphys has already requested some additional functionality here: Qiskit/rustworkx#150 (comment) which might not make it into 0.11 but definitely will be a priority for 0.12.

@Cryoris
Copy link
Contributor Author

Cryoris commented Dec 17, 2021

This issue is not mainly because I was encountering a particular feature gap, but I was more generally concerned about supporting networkx since it's more standardized 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature request New feature or request
Projects
None yet
2 participants