Forces re-calculating when doing incremental updates with no changes. about 3d-force-graph HOT 4 CLOSED

Alright I refactored my own code to only reassign graph data when there are topographical changes. For cosmetic line update I re-assign the link property accessors like linkColor, linkWidth, etc so that the graph will rerun those without reheating the simulation. Thanks for the help @vasturiano !

from 3d-force-graph.

@Blitzy thanks for reaching out.

The force simulation reheating is necessary in situations where the graph topology actually changed, so that it has the chance to find the new equilibrium in the nodes positions. But if you find the iterative motion of the nodes too distracting you can have them jump immediately to their final position by doing warmupTicks(50) (adjust to taste) and cooldownTicks(0).

What's not clear in your example is why do you need to update the data structure if there's no actual topology changes in your graph? In other words, if nothing changed in the data, why call graphData at all? This is causing the simulation to get reheated needlessly.

from 3d-force-graph.

That's a valid point and why I asked if I was using the feature in a way that was unintended. My plan moving forward is to treat it as you described, topographical changes.

Im storing a lot of state in the graph node and link data so updating it even if the topography didn't change was helpful. For instance, I'm changing the visual appearance of links based on custom properties I'm assigning to the link objects and updating the graph data seemed to be the most direct way to get the graph to update them.

from 3d-force-graph.

If you just need to do a cosmetic change, you don't need to reinvoke graphData but just the part that you updating, f.e. linkColor.

from 3d-force-graph.