-
Notifications
You must be signed in to change notification settings - Fork 37
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
node clustering feature has been dropped accidentally #102
Comments
@bburns632 -- I have been thinking: this orphan node clustering implementation is fairly janky, and from what I've seen, doesn't actually improve the layout of the graphs at all (it's all spaced as if the orphan nodes were still there). I think a better solution would be to set a threshold at which to remove the orphan nodes from the plot entirely. |
@jayqi Having seen a number of large graphs with 10+ orphan nodes, I agree the current clustering solution does not improve the layout of the graph. The graph is still sized with the original nodes included. However, I don't think eliminating them entirely from the report graph fits withe the goal of giving a full picture of a package. Let's explore hybrid solutions, maybe where orphan nodes are displayed in a separate pane or bullet pointed outside the visualization. This should only be an issue with the function graph, not the dependency graph. |
Agree with everything @bburns632 said. I think the biggest thing that annoys me about current orphan node handling is that we lay them all out horizontally, meaning that having a bunch of orphaned things leads to a tiny hard-to-read plot. The function and dependency graphs are fundamentally different graphs...dependency graph is a tree while the function graph is just a directed graph with an arbitrary number of connected components. I think that for orphan nodes, we should set a width in in 1 orphan
5 orphans
23 orphan nodes
^ nodes didn't line up perfectly, but you get the point |
I played around with some other igraph layouts. I think it doesn't make sense to use hierarchical layouts for See for lubridate: |
It seems as though node clustering has been removed as a feature in one of our recent PRs. Whoops.
We need to:
It was a minor feature, so not an urgent issue. However, it should be PR'd back in before v0.3
The text was updated successfully, but these errors were encountered: