The Negative That Doesn’t Mean Less · Motion Foundations · Lab Activity 2

Mode:
The rate machine — a velocity does something every secondhops, not formulas
A steady velocity is a promise: every second, the position changes by this many metres — sign and all. Set the promise, then press +1 second and watch it kept: one hop on the track, one new event in the table, one more piece of the line.
velocity v = m/s   start position x₀ = m
clock starts at t = s
Event table (one row per second)
Commit first — ink, then the machine.
The clock reads 2 s and the walker is at x = 1 m, moving at a steady +2.5 m/s. Where is the walker when the clock reads 6 s?
clock reading t = position x = this second:
Teacher: before each press, point at a student: where will it be after this second? Then press. Re-set with v = −1.5 from x₀ = 7 and repeat — the promise is kept leftward. No formula appears anywhere in this scene.
Two walkers, one meetingthe freeze-frame question
Walker A and Walker B walk along the same straight track. The graph plots both positions against the clock reading. Play the motion; it pauses itself at the moment they meet. Commit both answers in ink before Reveal.
t = 0.0 s
Closing in on an instantthe shrinking interval, from both sides
The walker’s motion follows the curve shown. The marked instant is t = 4 s. Each button computes an average velocity over an interval that ends — or begins — at that instant, and draws its chord. Commit before you press the two finest buttons.
Chords from the left (interval ends at 4 s)
Chords from the right (interval begins at 4 s)
Commit — ink first.
Every interval on those buttons has t = 4 s as one of its two ends. Will making such an interval small enough ever give an average velocity exactly equal to the velocity at t = 4 s?
Out and back — two averages, one journeythree freezes · commit at each
One walker: out fast, back slower. The motion pauses itself three times. At each pause, commit in ink, then press Continue. Reveal comes only at the end.
t = 0.0 s   x = 0.0 m
Builder — velocity editionsegments of steady velocity · pin a claim · resolve conflicts
Build a motion out of segments of steady velocity — each segment says: for this many seconds, the walker’s position changes by this many metres each second. Then pin a claim of your own (“at t = …, x = …”) and see whether your claims agree. The four cards are the judges.
Your model
Start position x₀ = m
Pin a claim
at t = s , x = m
Challenges
About this activity (provenance)

The difficulties this lesson works on are extensively documented in physics education research: the operational meaning of velocity as a rate (Arons, A Guide to Introductory Physics Teaching, Ch. 2), student understanding of velocity in one dimension (Trowbridge & McDermott, Am. J. Phys. 48, 1020 (1980)), connecting graphs to motion (McDermott, Rosenquist & van Zee, Am. J. Phys. 55 (1987); Beichner, Am. J. Phys. 62, 750 (1994)), and real-time graphing (Thornton & Sokoloff, Am. J. Phys. 58, 858 (1990)). The commit-before-reveal protocol follows the Interactive Lecture Demonstration tradition; step-level checking of student constructions goes back to the Andes physics tutor (VanLehn et al., Int. J. Artificial Intelligence in Education 15, 2005). This activity’s contribution is narrower: its rate machine, freezes and reveals are wired to the misconception bands of the FundaFirst HS Motion Foundations diagnostic, so what a class does here speaks the same language as its heatmap and remediation worksheet.