Angular variables as state vectors

Rotational motion has an angle, angular velocity, and angular acceleration. They play roles similar to position, velocity, and acceleration, but their units and geometry are different. An angle may be wrapped for display, while the unwrapped angle or accumulated turn count can remain necessary for a physical state/history; treating both as one unnamed number hides a data-loss decision.

Think like a programmer

Use a state object with named fields such as { angleRadians, angularVelocityRadPerSecond }, plus torque, inertia, timestamp, and coordinate-axis convention. Derive angular acceleration from torque in a pure function. Keep an unwrapped physical angle or turn counter for integration and event detection; use a separate tested wrap function only at a display boundary. This prevents mixing radians, radians per second, turns, and linear distances in a renderer or solver.

Model checklist

Inputs: Initial angle and angular velocity, torque model, moment of inertia, axis/sign convention, start/end time, time step/integrator, display wrap interval, and external-torque/boundary policy.
State: Timestamped unwrapped angle, optional display angle, angular velocity, angular acceleration, torque, angular momentum, kinetic energy, and turn/event count.
Rule: Compute α = τ/I from current inputs, update angular velocity and unwrapped angle with the declared integrator, then derive wrapped display angle without feeding it back into physics.
Output: Angular state trace, display orientation, momentum/energy diagnostics, wrap/event metadata, and refinement result.
Check: Zero torque gives zero angular acceleration; doubling inertia halves α for fixed torque; wrapping preserves orientation modulo 2π but not accumulated turns; one positive full turn maps to the same display angle with a different turn count; torque-free ideal angular momentum is bounded under refinement.

\[\tau=I\alpha,\qquad \omega=\frac{d\theta}{dt},\qquad L=I\omega,\qquad \theta_{display}=\theta\bmod2\pi\]

Sign convention must be named. In a two-dimensional model, choose whether positive angle and torque are counter-clockwise or clockwise relative to a specified screen/physics axis. Screen y often points down, but that visual coordinate does not require a physics sign reversal. Test one basis case: positive torque on a positive-inertia body must increase angular velocity under the chosen convention.

Wrapping is helpful for a dial or sprite orientation, but it creates discontinuities at 0 and 2π. Do not estimate angular velocity by naive finite differences of wrapped angles across that seam; use unwrapped state or a periodic-aware difference. Likewise, a controller that needs “three more turns” must not receive only the wrapped display value.

Try this experiment

Prediction: At fixed torque, increasing inertia reduces angular acceleration, while a full turn changes unwrapped state but not a wrapped display orientation.

Hold torque fixed and vary I. Record α, ω, and unwrapped θ after one step. Advance through one full turn, then compare unwrapped angle, turn count, and display angle. Test a finite-difference velocity estimate around the wrap seam and explain why the unwrapped state is the safer source. Finally reverse torque and predict the sign changes.

Where this model breaks

Angles can wrap around and 3D rotation needs more than one scalar angle. Rigid-body orientation often uses matrices or quaternions to avoid singular representations. The scalar relation τ = Iα assumes an appropriate fixed axis/inertia model; changing orientation, deformable bodies, gyroscopic coupling, friction, and distributed mass require richer dynamics.

Torque updates angular motion

Change torque and moment of inertia. The same torque produces less angular acceleration for a harder-to-rotate body.

Torque: 6 N·mMoment of inertia: 2 kg·m²

Torque 6 N·m; moment of inertia 2 kg·m²; angular acceleration 3.00 rad/s²; rotational energy at 3 rad/s 9.00 J.

Try this experiment

Prediction: At fixed torque, increasing inertia reduces angular acceleration.

Change inertia while holding torque fixed. Identify the state field that would change on the next time step.

Where this model breaks

Angles can wrap around and 3D rotation needs more than one scalar angle. Rigid-body orientation often uses matrices or quaternions to avoid singular representations.

Summary

Store rotational state explicitly, keep units and sign conventions visible, retain unwrapped physics state, and use wrapping only for display. Test zero torque, inertia scaling, wrap seam behavior, and torque-free diagnostics under refinement.

Glossary

Angle: rotational position, commonly in radians.
Angular velocity: rate of change of angle.
Angular acceleration: rate of change of angular velocity.
Unwrapped angle: continuous accumulated rotation retained by the physical state.
Wrap seam: discontinuity in a displayed angle where 2π maps back to 0.

Self-check

What angular state does torque update first?
Which unit distinguishes angular velocity?
Why should wrapping be a display adapter rather than integration state?
Why is one angle insufficient for general 3D orientation?

Sources

OpenStax, University Physics Volume 1, rotational motion chapter.
J. B. Marion and S. T. Thornton, Classical Dynamics of Particles and Systems.

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 Angular Variables as State Vectors, write down the quantities you can control, the values your program must retain, and the result a reader could inspect. In Rotational 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 Angular Variables as State Vectors 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 Angular Variables as State Vectors into a test

Represent angle and angular velocity as rotational state, then distinguish them from the linear quantities they resemble.

Name the inputs and units that the rotational motion 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.

Share to: