Go back to position Verlet?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- data-visualization
Research direction
Read the force layout’s integration code and compare its behavior with the linked D3 3.x examples: https://bl.ocks.org/mbostock/7881887 and https://observablehq.com/@d3/clustered-bubbles-2. The issue proposes reconsidering position Verlet because the current method feels more sluggish, while noting that changing integration would disrupt custom forces; done would require a considered decision about whether to make that change.
Written by the indexing model from the issue text.
Description
When this module was broken out for D3 3.x, we switched from position to velocity Verlet. I believe the idea was to avoid certain ordering effects and instabilities as a result of forces incrementally modifying node positions as they ran. However, the new force layout feels… more sluggish than the old one. Here’s an example:
https://bl.ocks.org/mbostock/7881887
https://observablehq.com/@d3/clustered-bubbles-2
Going back to the D3 3.x method of integration would be disruptive (for custom forces), but it’s worth considering.
- Dominant language
- JavaScript
- Stars
- 2k
- Forks
- 395
- Avg merge
- 5h 46m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from d3/d3-force
-
Difficulty 5/5 Over a week Newbie friendliness 18/100
-
`README` links to deprecated notebookPossibly taken @hirehamir claimed this 1200 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 20/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Similar issues
-
maintenance
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
assistant-ui/assistant-ui#10496 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
ai bug design good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
neomjs/neo-agent-institution#927 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gramps-project/gramps-web#1671 ·
Maintainers usually reply within 1 day
-
bug good first issue priority: P2 status: ready
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
RhinoLink-Tech/data-fabric#502 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
cline/mcp-marketplace#3708 ·