Skip to content
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

Graph drifts when there is a high degree on-circle node #30

Open
hasanbalci opened this issue Jun 24, 2021 · 1 comment
Open

Graph drifts when there is a high degree on-circle node #30

hasanbalci opened this issue Jun 24, 2021 · 1 comment
Labels
bug Something isn't working

Comments

@hasanbalci
Copy link
Contributor

I observed that if a graph has a high degree on-circle node (green-bordered) as in the below image, than graph drifts excessively (more than 10000 pixels) both in randomized and incremental layout. However, in randomized case it drifts one time and then stays around that position, while in incremental case it continues drifting.
image

To reproduce:

  • Import this file with default settings and apply layout:
    CiSE_bug.graphml.txt
  • Move n1042802 to the cluster that contains n0
  • Uncluster n1042802's previous cluster (nodes connected to n1042802 except n0 should be unclustered
  • Adjust "Allow Nodes In Circles" to "Yes" and "Max Ratio Of Nodes Inside Circle" to 0.04 (this is optional, just to obtain the layout in the image)
  • When a layout is applied, graph drifts
@hasanbalci hasanbalci added the bug Something isn't working label Jun 24, 2021
@ugurdogrusoz
Copy link
Contributor

We suspect that this is due to very high degree nodes. The green bordered on-circle node is probably pulled very strongly towards unclustered gray nodes, causing the drift. Maybe we should apply a weighted approach (cluster nodes move slower than regular nodes) to node's movements if not already.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants