-
-
Notifications
You must be signed in to change notification settings - Fork 403
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
Shortest path functions with cutoff distance #2358
Comments
Note: what's required for direct betweenness is cutoff versions of |
This brings up an interesting question: Should the comparison with the cutoff be done with tolerances, even in the current functions? Do we get paths which are |
😬 There's probably going to be issues without tolerances, but I haven't seen them yet. I see IGRAPH_SHORTEST_PATH_EPSILON is used for comparisons. I think you want inclusive? Like if you say the cutoff is 3.0, then you want to include paths with length 3.0? To me that seems more usual than wanting everything below 3.0. |
Please skip the tolerances for now. I'll write later about why (on my phone). I think elsewhere we used <= cutoff, so let's use that here too for consistency |
What is the feature or improvement you would like to see?
igraph_distances(_dijkstra)()
has a cutoff version, which does not consider paths longer than a threshold value.This is a request to implement the same for
igraph_get_shortest_paths(_dijkstra)()
.Use cases for the feature
igraph_distances()
The text was updated successfully, but these errors were encountered: