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
I recently ran some code that was about a year old, and it ran into errors because tidygraph current (1.3.1) changed the behavior of as_tbl_graph() to no longer read name attributes from to and from columns of edgelists.
What seemed weird to me is that tbl_graph() works completely differently, reading the edgelist as node attributes.
# No names>edges %>% as_tbl_graph()
# A tbl_graph: 290 nodes and 41905 edges## A directed acyclic simple graph with 1 component## Node Data: 290 × 0 (active)## Edge Data: 41,905 × 3fromtoweight<int><int><dbl>1120.00968>edges %>% tbl_graph()
# A tbl_graph: 41905 nodes and 0 edges## A rooted forest with 41905 trees## Node Data: 41,905 × 3 (active)fromtoweight<dbl><dbl><dbl>11123588532110.0096821123589898980.00565
If this is intentional then I'm sorry for the superfluous report, but the changelog read to me as if there were some fixes lately related to similar issues.
The text was updated successfully, but these errors were encountered:
A data.frame containing information about the nodes in the graph. If edges$to and/or edges$from are characters then they will be matched to the column named according to node_key in nodes, if it exists. If not, they will be matched to the first column.
Because I had persisted my edgelist to csv and my node names are numerical IDs, the columns were autocast to dbl.
Hi, thanks for the wonderful tidygraph package.
I recently ran some code that was about a year old, and it ran into errors because tidygraph current (
1.3.1
) changed the behavior ofas_tbl_graph()
to no longer read name attributes fromto
andfrom
columns of edgelists.What seemed weird to me is that
tbl_graph()
works completely differently, reading the edgelist as node attributes.If this is intentional then I'm sorry for the superfluous report, but the changelog read to me as if there were some fixes lately related to similar issues.
The text was updated successfully, but these errors were encountered: