-
Notifications
You must be signed in to change notification settings - Fork 255
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
Complete the Python implementations of usability benchmarks #469
Comments
Hi, currently working on a PR for the following examples:
|
@yanchenm Thanks for offering to contribute! We created a new repository to host the solutions. You can open a pull request (a separate one for each task) there. https://github.com/igraph/usability-benchmarks This is still a new project, and we are still exploring the best way to move forward with it. Things may change rapidly. I would suggest opening a draft PR before you are completely done with the task. Create a new directory within |
I am working with @yanchenm, @ChenyanWang and @jamesjiang52 on this issue and I completed the visualize cliques task. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions. |
We have a set of usability benchmarks—a collection of small tasks that help us judge how convenient it is to use the library. This issue is to implement each such task using python-igraph.
https://github.com/igraph/usability-benchmarks
This collection of solutions will also be useful as a "dictionary" that helps users familiar with another high-level interface of igraph (or even a different graph library) get up to speed with python-igraph.
Ideally, the Python solutions would eventually be collected into a Jupyter notebook: this way usability in notebook environments could also be explored.
If you plan to work on this issue, choose one or a few exercises of your liking, and post a comment noting which ones you will be implementing.
The text was updated successfully, but these errors were encountered: