A Byte of PhysicsLogo

Precession and nutation

Precession is the turning of a rotating body's axis around another direction. Nutation is the accompanying variation of the tilt angle. A spinning top can therefore have three simultaneous angular motions: rapid spin about its own symmetry axis, slower precession of that axis, and an up-and-down nutational wobble.

Compare the two views in Figure 1. In panel (a), the small loop around the shaft indicates spin, while the large dashed ellipse shows the axis sweeping around the vertical. Panel (b) plots tilt against time: its rising and falling curve represents nutation. That curve is a history of one angle, not the top's path through space.

Three angles describe a symmetric top

For a top with one point fixed, a common Euler-angle description uses:

Their time derivatives are not simply the Cartesian components of angular velocity. Figure 1 helps distinguish them: motion around the large ellipse changes the precession angle, rotation about the shaft changes the spin angle, and the right-hand trace changes the tilt. With steady precession and no nutation, that tilt trace would be horizontal.

Euler-angle formulas depend on the chosen rotation order and become singular at some orientations. A rotation matrix or quaternion is usually safer for general numerical orientation, while Euler angles remain useful for interpreting precession and nutation.

import numpy as np

tilt, phase, spin_phase = np.deg2rad(20), 0.3, 2.0
axis = np.array(
    [np.sin(tilt) * np.cos(phase), np.sin(tilt) * np.sin(phase), np.cos(tilt)]
)
print("Top axis in world coordinates:", axis)

Gravity torque about the pivot

Let the center of mass be distance \(d\) along the symmetry axis from the fixed pivot. Gravity produces torque

\[\boldsymbol\tau=\mathbf r_{\mathrm{cm}}\times M\mathbf g\]

If the tilt from upward vertical is \(\theta\), the torque magnitude is

\[\tau=Mgd\sin\theta\]

Torque is horizontal and perpendicular to the plane containing the vertical and body axis. It changes the direction of angular momentum, producing precession rather than an instantaneous fall directly along the torque direction.

Steady precession approximation

During steady precession, tilt remains constant while angular momentum turns around the vertical at angular speed \(\Omega\). If spin angular momentum dominates and is nearly along the body axis,

\[L_s\approx I_s\omega_s\]

The direction-change rate is approximately

\[\left|\frac{d\mathbf L}{dt}\right|\approx\Omega L_s\sin\theta\]

Equating it with gravitational torque gives

\[\Omega\approx\frac{Mgd}{I_s\omega_s}\]

Faster spin therefore produces slower precession under the same gravity torque. Reversing spin reverses the precession direction with a fixed geometry convention.

This relation is not exact for every top. It assumes rapid spin, approximate axial symmetry, fixed pivot, and steady tilt, and it neglects angular momentum associated with precession itself. The full steady-precession condition can have different branches and must be solved from rigid-body dynamics when precession is not slow compared with spin.

mass, gravity, offset, inertia, spin = 0.5, 9.81, 0.1, 0.002, 200.0
spin_momentum = inertia * spin
if abs(spin_momentum) < 1e-8:
    raise ValueError("The fast-top approximation needs substantial spin.")
precession_rate = mass * gravity * offset / spin_momentum
print(f"Steady-precession estimate: {precession_rate:.3f} rad/s")

Why nutation occurs

Steady precession is one special initial condition. If a spinning top is released with a precession rate that does not match that condition, gravity changes both the direction of angular momentum and the relation between angular momentum and the body axis. Tilt then oscillates between turning angles: this is nutation.

Nutation is not necessarily evidence of numerical instability. It is a physical mode of the ideal top. Numerical error is diagnosed by checking whether nutation amplitude, period, energy, and conserved angular-momentum components converge as the step is reduced.

A top released with its axis tilted but with no initial precession commonly nutates rather than entering smooth steady precession immediately. Damping can reduce the wobble, but it also transfers energy and angular momentum through air resistance or the pivot.

Conserved quantities in the ideal symmetric top

For an axisymmetric top in uniform gravity with a fixed frictionless pivot, total mechanical energy is conserved. Gravity is invariant under rotation around the vertical, so the vertical component of angular momentum is conserved. Axial symmetry of the body also makes the component of angular momentum along the body symmetry axis conserved when there is no torque component along that axis.

These conserved quantities constrain tilt motion. The energy can be rearranged into a one-dimensional effective problem for \(\theta\). Allowed tilt values are those for which the effective kinetic energy is nonnegative; equality identifies nutation turning angles. A steady-precession solution corresponds to constant tilt at an appropriate stationary point of the effective potential.

Potential energy for one common angle convention is

\[U(\theta)=Mgd\cos\theta\]

Changing whether the center lies along or opposite the body-axis vector, or measuring tilt from downward vertical, changes the written sign. The force and geometry must agree with the convention.

Direction checks

Cross products determine precession direction. Choose the world vertical, pivot-to-center vector, gravity direction, and spin direction explicitly. Calculate torque with the right-hand rule, then add a small torque impulse to angular momentum. The new momentum direction predicts the early precession direction.

gravity_force = np.array([0.0, 0.0, -mass * gravity])
torque = np.cross(offset * axis, gravity_force)
angular_momentum = spin_momentum * axis
updated_l = angular_momentum + torque * 0.001
print("Torque (N m):", torque)
assert np.isclose(updated_l[2], angular_momentum[2])

Reversing the spin changes angular momentum but not gravitational torque at the same orientation, reversing the directional response. Reversing cross-product order would also reverse the result, but that would be a calculation error rather than new physics.

Damping and long-term behavior

Air drag and pivot friction remove mechanical energy. They may also exert external torque on a top-only system, reducing spin angular momentum. Since the fast-top approximation places spin rate in the denominator, decreasing spin can increase precession rate before the approximation eventually fails and the top falls.

The exact late behavior depends on friction law and contact. Modeling damping as a simple torque proportional to angular velocity is an approximation whose frame and affected components must be stated. Removing energy while artificially preserving every angular- momentum component is generally inconsistent for an externally damped top.

Free-body precession

Precession does not require gravity or a pivot. A torque-free nonspherical rigid body can have its body axes precess around a fixed angular-momentum vector because angular momentum and angular velocity are not generally parallel. In the inertial frame, \(\mathbf L\) remains constant; the body changes orientation around it.

This free precession is distinct from gravity-driven precession. The intermediate-axis instability can produce dramatic tumbling even with zero external torque. A complete explanation must identify which vector is fixed and which axis is precessing.

Numerical orientation and angle extraction

Integrate the full rigid-body equations in a consistent frame. If angular momentum is stored in world coordinates and inertia in body coordinates, transform before solving for angular velocity. Update orientation with a method suited to rotations and monitor quaternion norm or rotation-matrix orthogonality.

Extract tilt from normalized vectors using a clamped dot product to prevent roundoff from placing an inverse-cosine argument slightly outside its allowed interval. Unwrap precession and spin angles before differentiating; wrapped angles contain artificial jumps.

Convergence and physical diagnostics

Use zero gravity as a torque-free fixture. Use a high-spin symmetric top to compare early precession with the approximation. Then perturb the steady initial condition and confirm that nutation features stabilize under refinement.

# Compare the fast-top prediction as spin changes. Nutation is omitted here.
for spin in [100.0, 200.0, 400.0]:
    rate = mass * gravity * offset / (inertia * spin)
    print(f"Spin {spin:.0f} rad/s -> precession {rate:.4f} rad/s")

Compare at equal physical times. A plausible wobble shape is not evidence if its frequency or conserved quantities change materially with the step.

Reliability checks

Precession is the directional response of angular momentum to torque; nutation is the tilt dynamics left when the motion is not exactly steady. Separating the three angular motions and their conserved quantities turns a vague "wobble" into a checkable rigid-body model.

A worked Python notebook

Compare the steady-precession part of a spinning top's motion across spin rates. The question for this calculation is precise: how does precession estimate change when we change spin angular speed, while keeping the other choices fixed? The earlier sections explain the physical relationship. Here we turn one part of that relationship into a calculation that you can run, inspect, and change in Google Colab.

This slice isolates precession; predicting nutation needs the full orientation dynamics and initial conditions. Keep that sentence beside the results. A formula can return a number outside its useful range, and a plotting library will usually draw that number without asking whether the physical assumptions still hold. The selected interval is from 100 to 400 rad/s. It gives us a specific domain to discuss instead of leaving the graph's range to a software default.

Use the notebook link above the lesson, run the setup cell, and then run the cells in order. The code below is also included there. NumPy handles the arrays of numerical values, SymPy keeps the equation symbolic, and Matplotlib draws the results. If these libraries or notebook cells are unfamiliar, start with Your first physics notebook.

State the relationship before choosing a graph

In this small example, q stands for spin angular speed, expressed in rad/s. The output is precession estimate, expressed in rad/s. The equation below uses the numerical values in those units. Any fixed coefficients therefore carry the units needed to make the relation consistent. A value supplied in another unit must be converted before it enters this expression.

\[f(q) = \frac{245.25}{q}\]

This is a function of one changing input. It is not a statement that the physical system has only one variable. We deliberately hold the other inputs fixed so that one cause of variation is visible. Changing several inputs at once would make it harder to tell which change produced the output difference. Write down the held-fixed choices before trying a different experiment.

At 250 rad/s, the expression gives 0.981 rad/s. This is our reference calculation. It is a prediction of the stated example, not a new measurement. Its displayed digits help us compare implementations. They should not be read as a claim that physical inputs are known to six significant figures.

import numpy as np
import sympy as sp
import matplotlib.pyplot as plt

q = sp.Symbol("q", real=True)
expression = sp.sympify("0.5*9.81*0.1/(0.002*q)", locals={"q": q})
reference_input = 250.0
reference_output = float(expression.subs(q, reference_input))
print("Input:", reference_input, "rad/s")
print("Predicted precession estimate:", reference_output, "rad/s")

sp.Symbol declares a mathematical symbol. It does not assign a numerical measurement to that symbol. subs then replaces the symbol with our chosen input, and float converts the resulting symbolic number into a standard Python numerical value. Keeping these steps separate lets us inspect the equation before numerical substitution. It also prevents a later plot from becoming the only surviving record of the model.

Compare a few cases you can explain

Before drawing hundreds of points, calculate three. The lower endpoint gives 2.4525 rad/s. The midpoint, at 250 rad/s, gives 0.981 rad/s. The upper endpoint gives 0.613125 rad/s. Read these together with the assumptions: they describe different choices of spin angular speed within the same example, with the other inputs held fixed.

These three values are a useful first check, but they do not establish the shape between them. Two endpoints can be equal even when the curve bends or oscillates in between. Likewise, a large change between endpoints does not tell us whether the relationship is linear. We need the equation and intermediate samples to answer those questions.

evaluate = sp.lambdify(q, expression, modules="numpy")
inputs = np.array([100.0, 250.0, 400.0])
outputs = np.asarray(evaluate(inputs), dtype=float)
outputs = np.broadcast_to(outputs, inputs.shape)
for input_value, output_value in zip(inputs, outputs):
    print(f"{input_value:.6g} rad/s -> {output_value:.6g} rad/s")
assert np.all(np.isfinite(outputs))

lambdify turns the symbolic expression into a numerical function. We explicitly select NumPy as its numerical backend so it can accept an array. The same expression now has two useful forms: one for algebra and one for calculating many cases. The assertion checks that the chosen inputs produce finite outputs. It would catch an infinity or an undefined numerical result, but a finite value can still be physically inappropriate.

Make a graph that answers the question

The horizontal axis shows spin angular speed; the vertical axis shows precession estimate. Every plotted point is a prediction of the same expression. We mark the reference case separately so that a reader can connect the earlier printed value to its place on the curve. The axis labels include units because a shape without a scale cannot tell us the size of a physical effect.

input_grid = np.linspace(100.0, 400.0, 301)
output_grid = np.asarray(evaluate(input_grid), dtype=float)
output_grid = np.broadcast_to(output_grid, input_grid.shape)
fig, ax = plt.subplots(figsize=(7, 4))
ax.plot(input_grid, output_grid, label="Stated model")
ax.scatter([reference_input], [reference_output], label="Reference case", zorder=3)
ax.set_xlabel("Spin angular speed (rad/s)")
ax.set_ylabel("Precession estimate (rad/s)")
ax.legend()
ax.grid(alpha=0.25)
fig.tight_layout()
plt.show()

Look for a sign change, a turning point, or a region where the curve becomes steep. Connect each feature to the expression rather than to the colour of the line. If the curve has a minimum or maximum, changing the input in opposite directions may have similar effects on the output near that point. If it is nearly straight over a short interval, a local linear approximation may be useful even when the complete expression is nonlinear.

Increasing the number of samples makes the line smoother and may reveal features that a coarse grid missed. It does not improve the physical inputs or enlarge the model's validity range. For quantities that can take only discrete values, use the line as a guide to the relationship and interpret only the allowed input values. A plotting function does not enforce such restrictions for you.

Measure the local sensitivity

A derivative asks a more specific question than the whole graph: how quickly does precession estimate change near the reference input? Its units are the output unit divided by the input unit. For this calculation, the derivative at 250 rad/s is -0.003924 in those ratio units. Locally, the output decreases as the input increases. This statement is local; the sign or size of the slope can be different elsewhere on the curve.

\[f'(q) = - \frac{245.25}{q^{2}}\]

For a small input change, multiply the derivative by that change to estimate the output change. Then compare that estimate with a fresh evaluation of the full expression. The distinction between these two calculations matters: the derivative gives a tangent approximation, while substitution evaluates the chosen expression at the new point.

slope_expression = sp.diff(expression, q)
slope_at_reference = float(slope_expression.subs(q, reference_input))
changed_input = 251.5
linear_prediction = reference_output + slope_at_reference * (
    changed_input - reference_input
)
full_prediction = float(evaluate(changed_input))
print("Symbolic derivative:", slope_expression)
print("Tangent prediction:", linear_prediction, "rad/s")
print("Full expression:", full_prediction, "rad/s")
print("Approximation difference:", full_prediction - linear_prediction, "rad/s")

Here the changed input is 251.5 rad/s. The tangent estimate is 0.975114 rad/s, while the full expression gives 0.975149 rad/s. If the two values are close, it means the chosen input change is small enough for this local approximation at this point. It does not mean the entire model is linear. If the slope is zero, a quadratic or higher-order term may supply the leading change instead.

This is also the beginning of uncertainty propagation. If the input has a small stated standard uncertainty, the magnitude of the slope times that uncertainty estimates one contribution to output uncertainty. Do not automatically use the same rule for a wide interval, a discontinuity, a turning point with zero first derivative, or several correlated uncertain inputs. Those situations need more of the model than one slope.

Check the derivative with numerical differences

We can estimate the same slope from values on either side of the reference point. Subtract the lower output from the upper output and divide by twice the input step. Parentheses are essential: the entire output difference must be divided by the entire input interval. Without them, Python can execute a different mathematical expression while still producing a plausible number.

The calculation below uses three decreasing step sizes. Each estimate is compared with the symbolic derivative, so the reference is independent of the numerical difference formula. Near an endpoint, it is acceptable here to evaluate a small extension only because the displayed mathematical expression is smooth there; such a check does not assert that extrapolated values describe additional physical cases.

input_span = 300.0
for fraction in [1e-2, 1e-3, 1e-4]:
    step = input_span * fraction
    upper = float(evaluate(reference_input + step))
    lower = float(evaluate(reference_input - step))
    numerical_slope = (upper - lower) / (2 * step)
    difference = numerical_slope - slope_at_reference
    print(f"step={step:.6g}: slope={numerical_slope:.6g}, difference={difference:.6g}")

For a smooth function, reducing the step often reduces the approximation error at first. Very small steps can eventually make subtraction of nearly equal floating-point values less reliable. Therefore “smaller” is not an unlimited guarantee of “better.” Compare the observed behaviour over a useful range of steps instead of choosing the smallest number the computer can represent.

An absolute slope difference is useful when the expected slope is near zero. A relative difference would divide by a very small reference and could look enormous even when the absolute discrepancy is tiny. Away from zero, a relative difference can help compare quantities with very different scales. The tolerance should reflect the question and the numerical method, rather than a universal decimal threshold copied into every test.

Change the example and preserve the reasoning

Make one copy of the reference calculation before editing it. Choose a second value of spin angular speed inside the stated interval, predict whether precession estimate will rise or fall, and then evaluate the expression. Place the prediction and the result in a text cell. If they disagree, identify whether the mistake was in the sign, the unit conversion, the algebra, or the assumption about how the curve behaves.

Next choose a shorter plotting interval around the reference point. Compare the local curve with its tangent approximation. Then widen the interval again. The difference shows why a useful local estimate need not describe the whole range. Keep the axis labels and numerical scale visible when comparing the plots; automatic axis limits can make two different effects appear equally large.

Finally, return to the physical limit stated at the start: This slice isolates precession; predicting nutation needs the full orientation dynamics and initial conditions. Describe one change to the setup that would violate that limit. State what new input, equation, or observation would be needed before trusting an answer in the changed situation. This last step connects the Python experiment to the physics instead of treating successful execution as the only criterion for a useful result.

Before saving, restart the runtime and run all cells in order. A result that depends on an earlier, now-deleted input cell is not reproducible from the saved notebook. Keep unrounded values for later calculations, round only the reported output, and label any new data as measured, assumed, or generated. The graph and printed values should remain traceable to the same expression and the same choices of inputs.

Recover the output change by integrating the slope

There is another way to check that the expression and its derivative describe the same relationship. Add up the small output changes predicted by the slope across the chosen input interval. In the continuous limit, this integral equals the output at the upper endpoint minus the output at the lower endpoint. The result has units of rad/s: the input unit in the integration cancels the input unit in the denominator of the slope.

This statement is about the mathematics of this particular relationship. It does not assign a new physical meaning to an arbitrary area under a graph. For example, an area under force versus distance represents work, while an area under a different pair of quantities may represent something else or have no standard name. Always carry the axis units through the calculation before naming an integral.

slope_function = sp.lambdify(q, slope_expression, modules="numpy")
endpoint_change = float(evaluate(400.0) - evaluate(100.0))
for points in [101, 201, 401]:
    grid = np.linspace(100.0, 400.0, points)
    slopes = np.asarray(slope_function(grid), dtype=float)
    slopes = np.broadcast_to(slopes, grid.shape)
    integrated_change = np.trapezoid(slopes, grid)
    print(
        points,
        "integrated change:",
        integrated_change,
        "endpoint change:",
        endpoint_change,
    )

The trapezoidal rule joins neighbouring slope samples with straight segments and adds their signed areas. A negative contribution remains negative; replacing every slope by its magnitude would calculate a different quantity. Increasing the sample count provides a practical refinement check. If the values do not settle toward the endpoint difference, first inspect the interval, singularities, and array ordering.

Do not conclude that two agreeing calculations prove the model is physically complete. Both use the same selected relationship, so an omitted effect would be omitted from both. Their agreement is evidence that the numerical tools implement that relationship consistently. Comparing with an independent experiment or a more appropriate physical model is a separate test.

Keep this comparison in the notebook when you change the expression. It is particularly useful after adding a coefficient, changing a sign convention, or converting an input unit. A code cell that produces a smooth graph can conceal these mistakes; a second calculation of the same output change gives you another place to notice them.

Sources

Share to: