Symmetry and conservation
When a model's rules do not change under a transformation, a conserved quantity often follows. Time-translation symmetry is connected to energy conservation in the appropriate physical setting.
Think like a programmer
Model checklist
- Inputs
- A model rule, its allowed transformations, and system boundary.
- State
- Quantities claimed to be conserved.
- Rule
- Run equivalent conditions and evaluate invariants.
- Output
- Evidence for or against conservation within tolerance.
- Check
- Closed no-loss energy model keeps total energy fixed.
Energy as an accounting check
Set mass and height. In this no-loss model, gravitational potential energy becomes kinetic energy at ground level.
Potential energy 98.07 J; predicted landing speed 9.90 m/s; kinetic energy 98.07 J.
Compare transformed input packets
A symmetry is an operation (T) that leaves the model rule unchanged in the relevant sense. For an update function (F), a useful programmer-facing test is:
\[F(T\mathbf y,t)=T\,F(\mathbf y,t), \qquad I(\mathbf y_{n+1})\approx I(\mathbf y_n).\]The first relation tests equivariance of the rule; the second tests a claimed invariant (I). They are related ideas, not interchangeable assertions. Serialize original and transformed inputs, run the same solver configuration, transform one output back when needed, and compare a named norm with a scale-aware tolerance.
Examples are concrete: translating an isolated system should not change relative dynamics; rotating an isotropic central-force setup should rotate the answer; adding a constant to a potential should not change forces or energy differences; and shifting the time origin of an autonomous model should preserve the same trajectory up to the shift. Each requires matching boundaries and initial data.
A discrete program can break a continuous ideal
Finite grids may prefer horizontal and vertical directions, fixed time steps can break exact time-translation behavior, clipping or collision events can be discontinuous, and an external drive or thermostat is an intentional boundary transfer. Log the transformation, discretization, integrator, boundary conditions, and invariant residual rather than attributing all drift to “broken symmetry.”
Use analytic or hand-checkable fixtures first. Then refine grid and time step at a fixed physical observation time. A decreasing residual supports the implementation; a stable nonzero residual may instead reveal a real external source, an omitted subsystem, or a model assumption that needs to be named. Noether’s theorem gives a precise continuous-action result, so use it as guidance for model design rather than a blanket claim that any visually symmetric code conserves energy.
Try this experiment
Prediction: Changing the choice of energy reference does not change an energy difference.
Compare two heights, then imagine adding the same constant to both potential-energy values. Identify the unchanged physical prediction.Where this model breaks
Summary
Use transformations to create paired solver tests and invariants to create residual tests. Declare discretization and boundaries, then refine at fixed physical times before connecting a computational pattern to a conservation law.
Glossary
- Symmetry: transformation leaving a model's rules unchanged.
- Conservation law: invariant quantity in an appropriate closed system.
- Noether's theorem: formal link between continuous symmetries and conservation laws.
Self-check
- What invariant does the energy lab test?
- What transformation leaves energy differences unchanged?
- Why can a numerical model break a continuous symmetry?
Sources
- E. Noether, Invariant Variation Problems (1918).
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 Symmetry and Conservation, write down the quantities you can control, the values your program must retain, and the result a reader could inspect. In Potential Energy and Conservation Laws, 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 Symmetry and Conservation 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
- Which values are inputs, and which values must remain state?
- What observable result would tell you the model is behaving as expected?
- Which assumption would you test first before applying the model to a real system?
Model review: turn Symmetry and Conservation into a test
Connect unchanged model rules to conservation tests, while stating the boundary between a teaching analogy and Noether’s theorem.
- Name the inputs and units that the potential energy and conservation laws model needs.
- Separate the state you must keep from values you can calculate when needed.
- Write one rule that maps the current state and inputs to an observable result.
- Choose a limiting case, unit check, invariant, or known result before trusting an output.
- State one assumption you would change before using this simplified model for a real decision.