• Add forceCenter.strength. #81
• Add forceSimulation.randomSource.
• All built-in forces are now fully deterministic (including “jiggling” coincident nodes). #121
• Improve the default phyllotaxis layout slightly by offsetting by one half-radius.
• Improve the error message when a link references an unknown node.
• force.initialize is now passed a random source.
• Use exact paths in imports.
• Add more tests. #17

• Fix bug when initializing nodes with fixed positions. (#135)

• Adopt ES 2015 syntax.
• Adopt ES Map in favor of d3-collection dependency.
• Add iterations argument to simulation.tick. Thanks, @vasturiano!
• Fix bug when initializing nodes with fixed positions. (#123) Thanks, @vasturiano!

This release adopts ES2015 language features such as for-of and drops support for older browsers, including IE. If you need to support pre-ES2015 environments, you should stick with d3-force 1.x or use a transpiler.

• Fix bug when initializing nodes with fixed positions. (#135)

• Add iterations argument to simulation.tick. Thanks, @vasturiano!
• Fix bug when initializing nodes with fixed positions. (#123) Thanks, @vasturiano!

• Housekeeping.

v1.1.1

Compare

Choose a tag to compare

• Add d3.forceRadial.
• Fix treatment of negative strengths in d3.forceManyBody. (#98) Thanks, @vasturiano!

• Allow forces to be isolated to a subset of nodes (#72).

• Fix bug where calling collide.radius had no effect. (#63)
• Improve error message when link references unknown nodes. (#62)

• Add module entry point to package.json.

• First stable release.
• Remove simulation.fix and simulation.unfix[All]; use node.fx and node.fy instead (#35).
• Rename simulation.drag to simulation.velocityDecay.

Changes since D3 3.x

The force layout d3.layout.force has been renamed to d3.forceSimulation. The force simulation now uses velocity Verlet integration rather than position Verlet, tracking the nodes’ positions (node.x, node.y) and velocities (node.vx, node.vy) rather than their previous positions (node.px, node.py).

Rather than hard-coding a set of built-in forces, the force simulation is now extensible: you specify which forces you want! The approach affords greater flexibility through composition. The new forces are more flexible, too: force parameters can typically be configured per-node or per-link. There are separate positioning forces for x and y that replace force.gravity; x.x and y.y replace force.size. The new link force replaces force.linkStrength and employs better default heuristics to improve stability. The new many-body force replaces force.charge and supports a new minimum-distance parameter and performance improvements thanks to 4.0’s new quadtrees. There are also brand-new forces for centering nodes and collision resolution.

The new forces and simulation have been carefully crafted to avoid nondeterminism. Rather than initializing nodes randomly, if the nodes do not have preset positions, they are placed in a phyllotaxis pattern:

<img alt="Phyllotaxis" src="https://raw.githubusercontent.com/d3/d3-force/master/img/phyllotaxis.png" width="420" height="219">

Random jitter is still needed to resolve link, collision and many-body forces if there are coincident nodes, but at least in the common case, the force simulation (and the resulting force-directed graph layout) is now consistent across browsers and reloads. D3 no longer plays dice!

The force simulation has several new methods for greater control over heating, such as simulation.alphaMin and simulation.alphaDecay, and the internal timer. Calling simulation.alpha now has no effect on the internal timer, which is controlled independently via simulation.stop and simulation.restart. The force layout’s internal timer now starts automatically on creation, removing force.start. As in 3.x, you can advance the simulation manually using simulation.tick. The force.friction parameter is replaced by simulation.velocityDecay. A new simulation.alphaTarget method allows you to set the desired alpha (temperature) of the simulation, such that the simulation can be smoothly reheated during interaction, and then smoothly cooled again. This improves the stability of the graph during interaction.

The force layout no longer depends on the drag behavior, though you can certainly create draggable force-directed graphs! Set node.fx and node.fy to fix a node’s position. As an alternative to a Voronoi SVG overlay, you can now use simulation.find to find the closest node to a pointer.

See CHANGES for all D3 changes since 3.x.

• Export to the global d3 in vanilla environments (d3/d3#2840).
• Add simulation.unfixAll (#33).

• Update d3-collection to 0.2.

• Add simulation.find.
• Treat strength as zero if x.x or y.y is NaN.

• Reduce the default link.strength on heavily-connected nodes (#30).
• Reduce the default manyBody.strength to -30.
• The link.strength and link.distance accessors are now passed the correct arguments.

• Add simulation.fix and simulation.unfix (#27).
• Add simulation.alphaTarget (#26).
• Add simulation.alpha.
• Optimize and area-bias d3.forceCollide to improve stability (#24 #25).
• Change the meaning of simulation.alphaDecay.
• Change simulation.restart to not affect the simulation’s alpha.

• Replace d3.forcePosition with d3.forceX and d3.forceY.
• Better resolution of exact coincidence along x or y, not just x and y (#23).
• Fix for exact coincidence in d3.forceCollide.
• A few optimizations.

• Fix bug in d3.forceLink initialization.

• Change the default simulation.alphaMin to 0.001.
• Optimize the initialization of d3.forceLink.
• Remove d3.forceContain.

• Rename simulation.start to simulation.restart.
• Add link.iterations and collide.iterations for more rigid constraints.
• Improve the stability of the d3.forceLink and d3.forceCollide forces.
• Increase the default link strength to 0.7.
• Decrease the default drag to 0.4.

• Change simulation.tick to always advance the simulation by one step, to not dispatch a tick event, and to return alpha < alphaMin. (The tick event is still dispatched by the simulation’s internal timer, which can be controlled via simulation.start and simulation.stop.)

• Deterministic initialization using phyllotaxis!
• Fix a bug implementing manyBody.distanceMin.

• Changed force.initialize to take an array of nodes, not the simulation.
• You can now pass a radius to d3.forceCollide.
• The links argument to d3.forceLink is now optional and defaults to the empty array.
• The nodes argument to d3.forceSimulation is now optional and defaults to the empty array.
• Removed the start event from simulation.on.
• Fixed simulation.start, simulation.stop and simulation.tick; you can now tick manually.

• Rename simulation.friction to simulation.drag.
• Improve stability of circle collisions.

• Increase the stability of d3.forceCollide.
• Don’t require nodes when creating a new d3.forceSimulation.
• Significantly improve the accuracy of d3.forceManyBody.
• Recompute strengths and distances when calling forceLink.links.