A Byte of PhysicsLogo

Numerical vs symbolic thinking

An exact equation can answer a carefully chosen question in one calculation. A numerical model trades that shortcut for a loop that also works when the exact equation is unknown.

Think like a programmer

Symbolic work is like simplifying a function before you run it. Numerical work is like running a small update function many times. The loop is flexible, but it has a step size and therefore an error.

Model checklist

Inputs
Time, gravity, and a time-step size in seconds.
State
Current position and velocity.
Rule
Add gravity to velocity, then add velocity to position.
Output
Position after two seconds.
Check
Compare with the exact constant-gravity result.

The exact distance after a release from rest is \(d=\\frac{1}{2}gt^2\). The numerical version uses a sequence of short updates instead.

velocity += gravity * timeStep;
position += velocity * timeStep;

Exact rule versus small steps

Euler result
22.073 m
Exact result
19.620 m
Error
2.453 m

Try this experiment

Prediction: A smaller time step will usually reduce the error.

Move the slider toward 0.02 seconds. Then move it toward 0.50 seconds. Record which result is closer to the exact answer and why the loop needs more work for a smaller step.

Where this model breaks

Euler stepping is deliberately simple. It can drift badly for long simulations or stiff systems. A better integrator changes the numerical error; it does not repair wrong forces or wrong units.

Summary

Use symbolic solutions when they are available and answer your question. Use numerical steps when you need flexibility, then measure the approximation against a known case.

Glossary

Self-check

  1. Which state values does the Euler loop store?
  2. What is the test oracle in this lesson?
  3. Why is a smaller step not automatically a better model?

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 Numerical vs Symbolic Thinking, write down the quantities you can control, the values your program must retain, and the result a reader could inspect. In Physics as Computation, 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 Numerical vs Symbolic Thinking 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 Numerical vs Symbolic Thinking into a test

Compare an exact falling-distance equation with a step-by-step numerical approximation and measure its error.

  1. Name the inputs and units that the physics as computation 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: