Closed squeetus closed 5 years ago
Modify any graph driver (with >100 nodes) and add the following call:
Why is it important the number of nodes is high? Is it becaue it is only implemented for the canvas backend?
Discover new academic papers with theAdvisor http://theadvisor.osu.edu/
Yep! It will be straightforward to modify the svg version too, but I didn't want to move too quickly before getting feedback
We should make the window parameters double. For the OSM case, we need high precision as the quantities within the window are very small in terms of degrees.
-- krs
On 2/9/19 6:01 PM, David Burlinson wrote:
Yep! It will be straightforward to modify the svg version too, but I didn't want to move too quickly before getting feedback
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/krs-world/bridges/pull/131#issuecomment-462087334, or mute the thread https://github.com/notifications/unsubscribe-auth/AFZSOBZKyHyM-Chrqa-QvAFlC83J5TjGks5vL1NmgaJpZM4ayvY_.
-- Kalpathi Subramanian Ph: 704 687 8579 Associate Professor Email: krs@uncc.edu Dept of Computer Science Web:http://webpages.uncc.edu/krs The University of North Carolina Charlotte, NC 28202-0001
@krs-world @esaule
Try pulling the 'window' branch and running code against the bridges-clone server:
bridges.setServer("clone");
Modify any graph driver (with >100 nodes) and add the following call:
bridges.setCoordSystemType("window");
and optionally specify the window:
bridges.setWindow(-100, 100, -100, 100);
If no window is specified, the graph-canvas script finds the 'extents' of the x and y axes, and projects them into the visualization view. If a window is specified, the script maps that window into the visualization view.
In addition, if all nodes in the vis are fixed (have a location specified), the alpha target ('heat' of the force simulation) is set to 0, which should ease up on the rendering somewhat. Note that zooming and panning will immediately reheat the simulation and will not perform well with lots of nodes/edges in the display, as will dragging or double-clicking a node.
Let me know what you think, and then we can merge the client code once we are happy with it.