A Byte of PhysicsLogo

Discrete vs continuous motion

Physics often describes motion as changing continuously. A computer stores and updates finite samples, so it needs a rule for what happens between one sample and the next.

Think like a programmer

A continuous model is the specification; discrete samples are the implementation strategy. The time step is a performance and accuracy setting, not a property of the object itself.

Model checklist

Inputs
Initial state, acceleration, total duration, and a time step.
State
Position and velocity at the current sample.
Rule
Advance the state one time step at a time.
Output
A sampled trajectory.
Check
Compare sampled motion with an analytic position function.
\[x(t)=x_0+v_0t+\\frac{1}{2}at^2\]

Exact rule versus small steps

Euler result
22.073 m
Exact result
19.620 m
Error
2.453 m

Try this experiment

Prediction: A coarse time step will make sampled motion differ more from the continuous reference.

Increase the time step, then reduce it. Connect the changing error to the number of updates the program performs.

Where this model breaks

Very small steps can still be slow, accumulate round-off error, or fail around collisions. Choose and test an integrator that fits the physical problem rather than only shrinking the step blindly.

Summary

Continuous equations describe a relationship for any time. Discrete code approximates that relationship at chosen samples and must report its numerical error.

Glossary

Self-check

  1. Which value controls the number of numerical updates?
  2. What is the continuous reference in this lesson?
  3. Why can a smaller step still be insufficient?

Sources

Model contract

Treat the lesson as a small function before treating it as a fact to memorize. Give every value a unit, keep only the state needed for the next step, and make the output easy to inspect.

\[\text{observable output} = f(\text{inputs},\,\text{state})\]
Inputs
Quantities you set or measure, with units and useful bounds.
State
Values the program must retain to reproduce the next result.
Rule
The relationship or update that turns inputs and state into a result.
Check
A known limit, unit check, invariant, or measured result that can expose a bad model.

Implement the idea as a model

For Discrete vs Continuous Motion, write down the quantities you can control, the values your program must retain, and the result a reader could inspect. In One-Dimensional Motion, the useful program is not the drawing: it is the smallest explicit model that makes a prediction you can test.

Guided experiment

Prediction: changing one declared input while holding the others fixed should change only the outputs that the model connects to that input. Choose one input, predict the direction of change, then check a limiting case such as zero, a symmetric arrangement, or a familiar low-speed or small-change approximation.

Where this model breaks

This lesson is a teaching model, not a complete simulator. Before using it outside the stated question, check which interactions, scales, uncertainties, boundary conditions, and measurement limits it leaves out.

Summary

Treat Discrete vs Continuous Motion as a contract: named inputs and units enter a rule, the rule produces an observable result, and a known limit or invariant checks whether the implementation deserves trust.

Glossary

  • Input: a measured value or chosen parameter supplied to a model.
  • State: the smallest set of values needed to continue or reproduce a model.
  • Validation: comparing an output with a known result, limit, invariant, or measurement.

Self-check

  1. Which values are inputs, and which values must remain state?
  2. What observable result would tell you the model is behaving as expected?
  3. Which assumption would you test first before applying the model to a real system?

Model review: turn Discrete vs Continuous Motion into a test

Compare smooth constant-acceleration motion with samples taken at different time intervals and identify approximation error.

  1. Name the inputs and units that the one-dimensional motion model needs.
  2. Separate the state you must keep from values you can calculate when needed.
  3. Write one rule that maps the current state and inputs to an observable result.
  4. Choose a limiting case, unit check, invariant, or known result before trusting an output.
  5. State one assumption you would change before using this simplified model for a real decision.
Share to: