Skip to content

Benchmark Problems

Benchmark problems are controlled calculations used to decide whether a notebook, solver, or plot can be trusted. The Mathematical Toolkit benchmark page owns the general numerical-method guidance. This page specializes that guidance to the Wave Mechanics and Model Systems volume.

A benchmark should state the Hamiltonian, boundary conditions, numerical method, reference result, refinement variable, and pass criterion before the computation is run.

IDBenchmarkNumerical TaskReference ResultPass CriterionCanonical Page
WMCS-B001Infinite square wellfinite-difference Hamiltonian eigenproblemEn=n2π2ℏ2/(2mL2)E_n=n^2\pi^2\hbar^2/(2mL^2)low-lying energies converge under grid refinement and eigenvectors are orthonormal in the grid inner productInfinite Square Well
WMCS-B002Harmonic oscillatordiagonalize a grid or basis HamiltonianEn=ℏω(n+1/2)E_n=\hbar\omega(n+1/2)low levels show constant spacing, expected parity, and negligible boundary-tail errorQuantum Harmonic Oscillator
WMCS-B003Finite square wellfind bound states by shooting or diagonalizationmatching equations and bound-state countenergies satisfy interface conditions and the number of bound states changes correctly with well depthFinite Square Well
WMCS-B004Free Gaussian packetevolve a localized wave packetanalytic width and conserved normnorm drift stays below the stated tolerance and σx(t)\sigma_x(t) follows the analytic spreading lawWave Packet Spreading
WMCS-B005Rectangular barrierpropagate or match a scattering statecurrent conservation and stationary transmission coefficientR+T=1R+T=1 within error and narrow packets agree with stationary transmission after momentum averagingRectangular Barrier Tunneling
WMCS-B006Landau levelscompute magnetic-field spectrum or construct Landau-gauge statesequal spacing ℏωc\hbar\omega_c and degeneracy A/(2πℓB2)A/(2\pi\ell_B^2)spacing, gauge convention, and finite-area degeneracy scaling are reported and checkedLandau Levels

Every benchmark run should include:

  • the physical parameters and unit convention;
  • the grid, basis, time step, solver tolerance, and finite domain;
  • the observable being compared, not only a plot;
  • an error estimate or convergence table;
  • a statement of which effects are finite-size, discretization, solver, or roundoff errors.

Typical pass criteria are scale dependent. A useful benchmark might require low-lying eigenvalue errors below 10−410^{-4} in chosen dimensionless units, norm drift below 10−1010^{-10} over a stated time window, or observed second-order convergence for a second-order finite-difference stencil. The numerical tolerance should be justified by the purpose of the notebook.

For finite-difference eigenproblems, check both energies and vector normalization. For a grid with spacing Δx\Delta x, a one-dimensional normalized state should satisfy

∑j∣ψj∣2Δx≈1.\sum_j \lvert\psi_j\rvert^2\Delta x \approx 1.

For closed-system time evolution, norm conservation is necessary but not sufficient. Also monitor energy expectation for time-independent Hamiltonians:

⟨H⟩(t)=⟨ψ(t)∣H∣ψ(t)⟩.\langle H\rangle(t) =\langle\psi(t)\vert H\vert\psi(t)\rangle.

For scattering benchmarks, use probability current. If the asymptotic wave numbers are kink_{\mathrm{in}} and koutk_{\mathrm{out}}, amplitudes alone do not define transmission:

T=joutjin.T =\frac{j_{\mathrm{out}}}{j_{\mathrm{in}}}.

For Landau-level calculations in a bulk region of area AA,

Nϕ=A2πℓB2,ℓB=ℏ∣q∣B.N_\phi =\frac{A}{2\pi\ell_B^2}, \qquad \ell_B=\sqrt{\frac{\hbar}{\lvert q\rvert B}}.

Finite geometry, edges, and boundary conditions can shift finite-size counts. A benchmark should state whether it tests the bulk formula, a finite rectangle, or a specific boundary convention.

A short benchmark report should include a table like this:

RunRefinement variableObservableReferenceErrorInterpretation
examplegrid spacing hhE1E_1exact well energyrelative errorchecks kinetic stencil and boundary rows
exampletime step Δt\Delta tnorm driftzero driftmaximum driftchecks time-stepper unitarity
exampledomain size LboxL_{\mathrm{box}}oscillator E0E_0ℏω/2\hbar\omega/2absolute errorchecks tail truncation

The interpretation column matters. A benchmark is not only a number; it is a diagnosis of what the computation has or has not tested.

  • Passing a benchmark at one grid size and calling it convergence.
  • Checking energy but not eigenfunction normalization or orthogonality.
  • Reporting norm conservation while the wave-packet width, phase, or transmission is wrong.
  • Comparing a finite-box calculation with an infinite-line formula without a domain-size study.
  • Forgetting that scattering probabilities are current ratios.
  • Testing a gauge-dependent wavefunction without stating the gauge.
  • Moving benchmark tolerances after a code change to make the result pass.
  • J. M. Thijssen, Computational Physics, 2nd ed., Cambridge University Press, 2007.
  • R. J. LeVeque, Finite Difference Methods for Ordinary and Partial Differential Equations, SIAM, 2007.
  • D. J. Tannor, Introduction to Quantum Mechanics: A Time-Dependent Perspective, University Science Books, 2007.
  • D. J. Griffiths and D. F. Schroeter, Introduction to Quantum Mechanics, 3rd ed., Cambridge University Press, 2018.
  1. A finite-difference infinite-well notebook reports the first five energies but does not check eigenvector orthogonality. Why is the benchmark incomplete?
Solution

The spectrum alone can look plausible even if the discrete inner product, boundary rows, or normalization convention is wrong. Orthonormality checks whether the finite matrix and grid weights correctly represent the Hilbert-space inner product. For a Hermitian discretized Hamiltonian, low-lying eigenvectors should be mutually orthonormal in the correct discrete inner product.

  1. A barrier-scattering notebook finds R+T=0.97R+T=0.97 for a conservative rectangular barrier. List two possible diagnoses.
Solution

The packet may not have fully separated from the barrier or boundaries, so reflected and transmitted probabilities have not been measured over complete regions. Alternatively, the numerical time evolution may not conserve norm well enough, absorbing boundaries may be present, or the coefficients may have been computed from amplitudes instead of currents.