Molecular dynamics advances particle positions and velocities from forces, then applies interaction and boundary rules. Its usefulness comes from explicit state, deterministic update order, and diagnostic ledgers—not from a cloud of animated dots. A molecular-dynamics program chooses a force model and an ensemble/boundary policy; those choices determine what energy and momentum conservation claims are valid.
Read the relationship as a short program. Begin with measured or chosen values, keep only the state needed for the next calculation, apply the stated rule, and inspect a result that can be checked independently.
import numpy as np
# Two Lennard-Jones particles; reduced units epsilon=sigma=mass=1.
positions = np.array([[-0.6, 0.0], [0.6, 0.0]])
velocities = np.array([[0.0, 0.1], [0.0, -0.1]])
def forces(positions):
offset = positions[1] - positions[0]
radius = np.linalg.norm(offset)
if radius < 0.2:
raise ValueError("Separation is too small for this demonstration step.")
radial_derivative = 24 * (radius**-7 - 2 * radius**-13)
first_force = radial_derivative * offset / radius
return np.array([first_force, -first_force])
assert np.allclose(forces(positions).sum(axis=0), 0.0)
print("Initial forces:", forces(positions))
For a conservative pair model, force comes from potential energy. A common programming contract is to define one potential \(U(r)\), derive or separately verify its radial force, then sum without double-counting pairs:
\[\mathbf F_{ij}=-\nabla_{\mathbf r_i}U(r_{ij}),\qquad \mathbf F_{ji}=-\mathbf F_{ij},\qquad E=\sum_i\tfrac12m_i\lVert\mathbf v_i\rVert^2+\sum_{i<j}U(r_{ij})\]The \(i < j\) convention is not cosmetic: it prevents counting each pair’s potential twice. Force symmetry is a cheap unit test. If a pair loop gives forces that do not sum to zero, total momentum drift may be caused by implementation order rather than an external force. A cutoff, neighbour list, or periodic minimum-image rule changes the approximation and must be stored with the run.
Boundaries define the system. Periodic boundaries exchange neither momentum nor energy with an outside world in the usual ideal model; a reflecting wall transfers momentum to the wall; a thermostat intentionally exchanges energy; an imposed shear or temperature gradient is a driven nonequilibrium system. Do not report “energy is not conserved” without first checking whether the model includes one of those transfers.
Time step is a physical-numerical compromise. Close repulsive encounters can make a pair potential stiff, so a visually stable run can still have unacceptable energy drift. Hold initial state and output times fixed, then reduce Δt. Compare total-energy drift, momentum residual, minimum separation, and selected aggregate observables. If a thermostat is active, compare the correct extended ledger rather than demanding closed-system energy conservation.
A useful check starts with a prediction: Changing update order inside an interaction loop can create a fake asymmetry, while a synchronous equal-and-opposite pair pass preserves total internal force. Write a two-particle force fixture and assert \(F1 + F2 = 0\). Run the same initial state with Δt, Δt/2, and Δt/4, recording energy and momentum residuals at identical physical times. Then switch from periodic boundaries to a reflecting wall and identify the wall impulse that belongs in the momentum ledger. Finally enable a thermostat and state why a closed-energy assertion is no longer the right test.
The explanation above has deliberate limits. Small steps can be expensive, close collisions can be stiff, and simple pair potentials omit real chemistry and quantum behavior. Finite particle counts, cutoff artifacts, long-range interactions, neighbour-list update errors, rigid constraints, phase changes, electronic structure, and non-equilibrium driving may require richer methods. Agreement of a few conservation diagnostics does not validate a chosen potential against a real material.
The Lennard–Jones model is a common teaching example:
\[U(r)=4\varepsilon\left[\left(\frac{\sigma}{r}\right)^{12}-\left(\frac{\sigma}{r}\right)^6\right]\]The parameter \(\varepsilon\) sets the well depth and \(\sigma\) sets the separation where the potential crosses zero. The radial force magnitude follows from \(F_r=-dU/dr\). At very small separation the repulsion becomes extremely steep, demanding a smaller time step. This potential is an approximate effective interaction, not a chemical bond model.
Truncating interactions at a cutoff saves work but changes both force and energy. Abruptly cutting the potential makes it discontinuous; merely shifting its value makes energy continuous but does not make force continuous. Record whether the potential, force, or both were shifted and test behavior near the cutoff.
A widely used time-reversible, second-order method is velocity Verlet. For acceleration \(\mathbf a_n\),
\[\mathbf r_{n+1}=\mathbf r_n+\mathbf v_n\Delta t+\frac12\mathbf a_n\Delta t^2\]After forces are recomputed at the new positions,
\[\mathbf v_{n+1}=\mathbf v_n+\frac12(\mathbf a_n+\mathbf a_{n+1})\Delta t\]dt = 0.001
initial_momentum = velocities.sum(axis=0)
for _ in range(1000):
old_acceleration = forces(positions)
new_positions = positions + velocities * dt + 0.5 * old_acceleration * dt**2
velocities += 0.5 * (old_acceleration + forces(new_positions)) * dt
positions = new_positions
assert np.allclose(velocities.sum(axis=0), initial_momentum)
print("Final positions:", positions)
Do not update one particle completely and then use its new position while other particles still have old positions. That asynchronous order violates the intended simultaneous force snapshot and can make results depend on storage order.
Periodic boundaries model an infinite repeated cell. A particle crossing one side is wrapped to the opposite side without changing physical velocity. Pair separation uses the nearest periodic image. For a box length \(L\), each Cartesian separation component can be mapped into a centered interval before force evaluation.
The usual minimum-image method requires a pair cutoff no larger than half the shortest box length. Otherwise more than one image may lie within the cutoff. Long-range electrostatic forces need specialized summation methods rather than a naive short cutoff.
Wrapping makes particle coordinates discontinuous at a boundary. Keep unwrapped coordinates or image counters when measuring diffusion; otherwise a particle traveling steadily across the box appears to jump backward.
An isolated constant-particle, constant-volume, constant-energy calculation approximates the microcanonical ensemble. A thermostat aims to sample a target-temperature ensemble by exchanging energy with a reservoir. It intentionally breaks conservation of the particle system's energy.
Simple velocity rescaling can force the instantaneous kinetic temperature to a target but may distort the velocity distribution and dynamics. More advanced deterministic or stochastic thermostats have their own parameters and sampling properties. Always report thermostat energy transfer and validate the resulting distribution, not only its mean temperature.
Equilibration data should normally be separated from production measurements. Starting from a lattice or an arbitrary velocity draw creates transients. Decide equilibration using observable histories and correlation times rather than deleting a convenient fixed number of steps without inspection.
Temperature, pressure, radial distribution, and diffusion are derived from trajectories. Their samples are correlated. Estimate uncertainty from block averages or independent runs, not by treating every time step as independent.
The radial distribution function measures pair separation statistics relative to an uncorrelated reference. For a uniform ideal gas it approaches one away from finite-size and boundary effects. Peaks in an interacting fluid reveal preferred neighbor distances; they are statistical structure, not fixed bonds.
Mean-square displacement can estimate diffusion at long times:
\[D=\lim_{t\to\infty}\frac{\langle|\mathbf r(t)-\mathbf r(0)|^2\rangle}{2dt}\]Use unwrapped positions and verify a linear long-time regime before fitting. Ballistic short-time motion does not satisfy the diffusive approximation.
Start with two particles and compare the coded force with a numerical derivative of the potential. Require equal and opposite forces. Move both particles by the same vector in a periodic cell and require unchanged energy. Permute their storage order and require the same physical output.
For a closed conservative run, compare total momentum and total energy at fixed physical times using \(\Delta t\), \(\Delta t/2\), and \(\Delta t/4\). Velocity Verlet should show second-order trajectory convergence over a fixed interval, although long chaotic trajectories separate and should instead be compared statistically.
Test neighbor lists against an all-pairs oracle for a small configuration, especially after particles move near the list skin distance. Track minimum separation and reject non-finite forces before they contaminate the full state. With reflecting walls, include wall impulse in momentum accounting. With a thermostat, test its energy ledger and target distribution rather than demanding particle-energy conservation.
Molecular dynamics remains classical unless quantum effects are added through another method. Pair potentials can omit electronic polarization, reactions, many-body forces, and nuclear quantum behavior. Conservation and numerical convergence validate an implementation; comparison with material data validates the physical potential.
Inspect the repulsive core and attractive tail of a two-particle Lennard-Jones interaction. The question for this calculation is precise: how does Lennard-Jones potential change when we change pair separation, 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.
Reduced units set the length and energy scales to one; a cutoff policy changes the implemented model. 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 0.95 to 3 reduced length units. 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.
In this small example, q stands for pair separation, expressed in reduced length units. The output is
Lennard-Jones potential, expressed in reduced energy units. 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.
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 1.2 reduced length units, the expression gives -0.890965 reduced energy units. 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("4*(q**-12-q**-6)", locals={"q": q})
reference_input = 1.2
reference_output = float(expression.subs(q, reference_input))
print("Input:", reference_input, "reduced length units")
print("Predicted Lennard-Jones potential:", reference_output, "reduced energy units")
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.
Before drawing hundreds of points, calculate three. The lower endpoint gives 1.96097 reduced energy units. The midpoint, at 1.975 reduced length units, gives -0.0662639 reduced energy units. The upper endpoint gives -0.00547944 reduced energy units. Read these together with the assumptions: they describe different choices of pair separation 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([0.95, 1.975, 3.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} reduced length units -> "
f"{output_value:.6g} reduced energy units"
)
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.
The horizontal axis shows pair separation; the vertical axis shows Lennard-Jones potential. 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(0.95, 3.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("Pair separation (reduced length units)")
ax.set_ylabel("Lennard-jones potential (reduced energy units)")
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.
A derivative asks a more specific question than the whole graph: how quickly does Lennard-Jones potential change near the reference input? Its units are the output unit divided by the input unit. For this calculation, the derivative at 1.2 reduced length units is 2.21169 in those ratio units. Locally, the output increases 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{24}{q^{7}} - \frac{48}{q^{13}}\]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 = 1.21025
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, "reduced energy units")
print("Full expression:", full_prediction, "reduced energy units")
print(
"Approximation difference:",
full_prediction - linear_prediction,
"reduced energy units",
)
Here the changed input is 1.21025 reduced length units. The tangent estimate is -0.868295 reduced energy units, while the full expression gives -0.867848 reduced energy units. 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.
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 = 2.05
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.
Make one copy of the reference calculation before editing it. Choose a second value of pair separation inside the stated interval, predict whether Lennard-Jones potential 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: Reduced units set the length and energy scales to one; a cutoff policy changes the implemented model. 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.
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 reduced energy units: 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(3.0) - evaluate(0.95))
for points in [101, 201, 401]:
grid = np.linspace(0.95, 3.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.