Coupled translational–rotational motion

An object can move through space while rotating. Rolling without slipping links linear speed and angular speed, but they remain different state variables with different units.

Think like a programmer

Use one combined state object with linear and angular fields. A constraint relates fields after or during an update; it does not turn metres per second into radians per second without a radius parameter.

Model checklist

Inputs: Radius, linear position/velocity, angular position/velocity, and contact condition.
State: Linear and angular components.
Rule: Apply force and torque updates plus rolling relation.
Output: Consistent translational and rotational state.
Check: No-slip rolling satisfies v = rω.

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 a fixed angular speed, a larger radius gives a larger no-slip linear speed.

Use the rotational state values as a starting point and calculate radius × angularVelocity. Identify which new parameter the current lab does not expose.

Where this model breaks

Real rolling can slip, deform, lose energy, and have changing contact geometry. The relation v = rω applies only to no-slip contact at a chosen instant.

Summary

Keep linear and angular state distinct, then connect them with explicit constraints and a radius. Test the no-slip relation rather than assuming it.

Glossary

Rolling without slipping: contact condition relating linear and angular speed.
Angular speed: magnitude of angular velocity.
Coupled state: state variables updated through shared rules or constraints.

Self-check

What parameter connects v and ω?
Which condition makes v = rω valid?
What real effect can break it?

Sources

OpenStax, University Physics Volume 1, rolling motion chapter.

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 Coupled Translational–Rotational Motion, 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 Coupled Translational–Rotational 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

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 Coupled Translational–Rotational Motion into a test

Track linear and angular state together, then use a rolling constraint to connect speed and angular velocity without conflating them.

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: