You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I was using the shortest path function and I found something that seems to be a bug, usually the results are catalogued in the same way:
If the shortestpath does not exists because are in different components, return logical(0)
if is requested from the same node to the same node, like from x to x, it returns a vector like c(x)
if is requested from/to different nodes, a vector with their respective nodes
In get_multi_paths if we request node x to node x, we are getting logical(0) instead c(c), this is pretty important in the moment to recognize if the path exists or not.
Thanks for pointing this !
You're right, the behavior should be the same in get_path_pair and get_multi_paths functions when going from node x to node x.
I'll fix it asap
Hi, I was using the shortest path function and I found something that seems to be a bug, usually the results are catalogued in the same way:
logical(0)
c(x)
In
get_multi_paths
if we request node x to node x, we are gettinglogical(0)
insteadc(c)
, this is pretty important in the moment to recognize if the path exists or not.Thx!
The text was updated successfully, but these errors were encountered: