Mass position may be incorrect when amplitude is increased while sim is paused
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start by reproducing the issue on the One Dimension Screen using the six-mass, paused-simulation steps and compare the behavior after stepping forward and pressing Initial Positions. Trace the simulation state update triggered by the sixth normal-mode slider; done means mass positions immediately reflect amplitude changes while paused, consistently matching the corrected initial positions.
Written by the indexing model from the issue text.
Description
Test device
MacBook Air (m1 chip)
Operating System
12.0.1
Browser
Safari 15
Problem description
https://github.com/phetsims/qa/issues/733
Sometimes when the sim is paused and amplitude values are changed, the positions of the masses don't accurately reflect that change.
Steps to reproduce
This behavior is very inconsistent, but here are some steps that have worked for me:
- Open the One Dimension Screen
- Increase the number of masses to 6
- Press the pause button
- Move the slider for the 6th normal mode all the way up--the position of the masses barely changes. If you did not get this result, press the 'Reset All' button and follow the same steps again.
- Step forward a little and then press the 'Initial Positions' button. The initial positions are now correct for that amplitude value.
Visuals

I do not see this behavior in the flash version

- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
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 phetsims/normal-modes
-
dev:typescript priority:5-deferred
Difficulty 5/5 Over a week Newbie friendliness 15/100
phetsims/normal-modes#92 ·
-
status:blocks-sim-publication
Difficulty 1/5 Under an hour Newbie friendliness 55/100
phetsims/normal-modes#90 ·
-
dev:code-review
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
phetsims/normal-modes#89 ·
-
priority:5-deferred type:bug type:multitouch
Difficulty 3/5 1-2 days Newbie friendliness 42/100
phetsims/normal-modes#87 · 1 comment ·
-
priority:5-deferred type:performance
Difficulty 3/5 1-2 days Newbie friendliness 42/100
phetsims/normal-modes#84 · 1 comment ·
All issues in phetsims/normal-modes
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Design only Leadership Survey SLFS
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
bcgov/digital-journeys#2293 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
tursodatabase/turso#9405 ·
Maintainers usually reply within 1 day
-
Toolkit
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
API Bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ProjectSidewalk/SidewalkWebpage#5556 ·
Maintainers usually reply within 1 day