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
Right now, vertices are mapped to a standard 0 -> maxid coordinate system, and vertices are created for every index. this means that if you pass a graph with vertices from 1000 to 1100, you will produce a 1100 vertex graph. This seems awkward to me, and is especially awkward since if, say, you were to extract the subgraph of the vertices you actually want (here, I want 1000 to 1100), when I call fg.fetch.subgraph, it remaps my original 1000 to 1100 vertices to 0 to 100 instead. This means that I then cannot obtain vertices based on their true indices, and will need to in my program account for remapping the coordinate systems, which seems too complicated to expect regular users to do.
The text was updated successfully, but these errors were encountered:
ebridge2
changed the title
documentation for how to get vertex IDs from graphs
decide whether a better way to represent graph vertices is necessary
Jul 23, 2017
Right now, vertices are mapped to a standard 0 -> maxid coordinate system, and vertices are created for every index. this means that if you pass a graph with vertices from 1000 to 1100, you will produce a 1100 vertex graph. This seems awkward to me, and is especially awkward since if, say, you were to extract the subgraph of the vertices you actually want (here, I want 1000 to 1100), when I call fg.fetch.subgraph, it remaps my original 1000 to 1100 vertices to 0 to 100 instead. This means that I then cannot obtain vertices based on their true indices, and will need to in my program account for remapping the coordinate systems, which seems too complicated to expect regular users to do.
The text was updated successfully, but these errors were encountered: