-
Notifications
You must be signed in to change notification settings - Fork 61
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
Add Maximum matching algorithm in experimental #254
base: v1.2
Are you sure you want to change the base?
Conversation
…ed when not required
…nto maximum-matching
Looks great! The github CI failure isn't your issue -- it's because the CI is using an older GraphBLAS. I have an updated CI in the v1.2 branch now, and it uses a more recent GraphBLAS and works fine. I've also just posted a beta release of GraphBLAS 9.4.0. It has a new feature that will help to find JIT compiler errors, like the ones you encountered occasionally. If a JIT compiler error occurs, GraphBLAS returns an error code (a new one, GxB_JIT_ERROR), instead of the older strategy where I fallback to a generic kernel. |
That's great! I think I currently use GraphBLAS 9.4.0. I still have some things left to add/fix before losing the
|
@DrTimothyAldenDavis I believe it's ready for review! |
This PR introduces the Maximum Matching algorithm as presented in the paper: Distributed-Memory Algorithms for Maximum Cardinality Matching in Bipartite Graphs, using GraphBLAS operations.
TODO: