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.

Sign up for GitHub

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

Jump to bottom

Segfault in `maximum_weight_perfect_matching` when the graph does not have a perfect matching #10

Open

etiennedeg opened this issue May 2, 2024 · 0 comments · May be fixed by #11

Member

etiennedeg commented May 2, 2024 •

edited

Loading

That's really not a nice behavior :\

~~the fault seems to be on BlossomV.jl side mlewe/BlossomV.jl#25~~

Ok, in fact, the problem seems to originate from Blossom V itself, this is so bad :(

// Computes a perfect matching of minimum cost.
// NOTE: a perfect matching of finite cost must exist (otherwise the behaviour is not specified).

We can get around this by adding dummy edges with big weights.

etiennedeg linked a pull request

that will close this issue

fix blossom #11

Open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment