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
If deg_d[cur] is 0, this will give the wrong result. (It will follow an edge that belongs to another node.) If additionally this is the last vertex, it will overflow col_d. If walk_length is 1, it will just give you walks with very high vertex IDs. With longer walks it will segfault.
How is the algorithm supposed to handle nodes with no outgoing edges? Producing shorter walks when we hit such a node is probably out of the question. Maybe we could just keep repeating the same node then? That would be easy to implement at least.
The text was updated successfully, but these errors were encountered:
If
deg_d[cur]
is 0, this will give the wrong result. (It will follow an edge that belongs to another node.) If additionally this is the last vertex, it will overflowcol_d
. Ifwalk_length
is 1, it will just give you walks with very high vertex IDs. With longer walks it will segfault.The CUDA implementation is different, but I think it also generates incorrect walks:
How is the algorithm supposed to handle nodes with no outgoing edges? Producing shorter walks when we hit such a node is probably out of the question. Maybe we could just keep repeating the same node then? That would be easy to implement at least.
The text was updated successfully, but these errors were encountered: