-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Influence of locked nodes on layout #1137
Comments
In general, a physics layout will work in the way you want if and only if (1) it has internal modelling of locked nodes (or otherwise they just behave as though the node isn't locked but the actual position won't change) and (2) it has support for iterative runs. In 2.5 (currently prerelease but soon to be tagged and released), CoSE has improved mechanics for locked nodes (1) but it wouldn't be able to do (2). CoSE Bilkent supports (2) but I'm not sure about (1) yet. Cola supports (2) and now supports (1). Note that many layouts have been separated as external extensions for 2.5, like Cola -- which means layout releases can be more frequent and it's easier to make pull requests to layouts. |
Closing for now |
@wolfig So how do you resolve you issue ? |
@Does666: Actually I didn't solve this at all. In the end I used vis.js (https://visjs.org/) which provides the functionality I needed out of the box. |
Hi Cytoscape experts,
I'm playing around with cyotscape.js and available force.driven layouts. My network has about 650 nodes and edges. I do see desired results using cola (cose et al. work well too) and with all nodes unlocked. However, it is essential for me to have some nodes locked to give my network some anchor-points where free nodes should orient to. If I use locked nodes I do get the impression that these are ignored by any of the layout algorythms - the unlocked nodes tend to move away from the locked ones. If you like I can provide my sources.
Bug, feature or feature request???
Best regards WolfiG
P.S.: I worked with Gephi so far (lacking the online capabilities), where the forceatlas2 produces results similar to cola. There I was able to lock nodes and the network arranged to them.
The text was updated successfully, but these errors were encountered: