A Byte of PhysicsLogo

Electron bands

An isolated atom has discrete energy levels. Put many atoms into a periodic crystal and nearby atomic states split into many closely spaced allowed energies. At the scale of a solid, those groups are bands. The important output is not a cartoon of individual electrons hopping between atoms; it is the relationship between energy, crystal momentum, occupancy, and temperature.

Think like a programmer

A band diagram is the output of a parameterized eigenvalue problem. Store lattice spacing, potential parameters, the sampled k-grid, and a deterministic band-ordering rule. If changing the grid changes a claimed gap, the result has not converged.

Model checklist

Inputs
Lattice spacing, a periodic-potential model, crystal-momentum samples, temperature, and electron count.
State
The Hamiltonian parameters, sampled k values, and the ordered eigenvalues for every k.
Rule
Solve a Hermitian eigenproblem at each crystal momentum and sort the resulting energies.
Output
Energy bands E(k), occupied states, and an estimated band gap.
Check
Refining the k grid should not materially change the extrema used for the reported gap.

A minimal computational picture

In a one-dimensional tight-binding teaching model with one orbital per site, a single band can take the form

\[E(k)=E_0-2t\cos(ka)\]

a is lattice spacing, t is a coupling-energy parameter, and k is crystal momentum. This formula is not a universal material solver. It is useful because the extrema, bandwidth, and periodicity are visible and testable. Sample k in a fixed interval such as [-π/a, π/a], then compute min(E) and max(E) rather than trusting the line that happens to look highest on a plot.

const band = kValues.map((k) => energy0 - 2 * hoppingEv * Math.cos(k * latticeSpacing));
const widthEv = Math.max(...band) - Math.min(...band);

For several bands, the band gap is the difference between the lowest unoccupied conduction-band energy and the highest occupied valence-band energy:

\[E_g=\min(E_{\mathrm{conduction}})-\max(E_{\mathrm{valence}})\]

Check that the result is non-negative and report whether the extrema occur at the same k. That distinction separates a direct-gap diagram from an indirect-gap diagram in a simplified model.

From band data to material claims

A partially filled band lets electrons change to nearby available states under an electric field. A filled valence band separated by a large gap does not. Semiconductors have a smaller gap than typical insulators, so temperature and doping can change the carrier population. None of this means a band diagram alone predicts a device's current: contacts, scattering, geometry, and bias matter too.

Try this experiment

Prediction: Doubling the hopping magnitude doubles the width of this one-dimensional tight-binding band.

Hold a and E0 fixed. Plot the band for t = 1 eV and t = 2 eV, calculate both widths, then explain why the cosine's range makes the prediction testable.

Where this model breaks

The one-orbital, nearest-neighbor model omits multiple orbitals, disorder, electron interactions, phonons, spin effects, and realistic surfaces. Treat it as a model of periodic coupling, not as a predictive band-structure calculation for a named material.

Summary

Electron bands are arrays of eigenvalues indexed by crystal momentum. Build them reproducibly, verify grid convergence and band ordering, then state clearly which carrier and material effects the reduced model leaves out.

Glossary

Self-check

  1. Which values must be stored to reproduce a band calculation?
  2. Why should a gap report include k-grid convergence?
  3. What does a partially filled band allow that a filled band does not?

Sources

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 Electron Bands, write down the quantities you can control, the values your program must retain, and the result a reader could inspect. In Atoms and Solids, 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 Electron Bands 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

  1. Which values are inputs, and which values must remain state?
  2. What observable result would tell you the model is behaving as expected?
  3. Which assumption would you test first before applying the model to a real system?

Model review: turn Electron Bands into a test

Sample periodic solid models reproducibly and verify band ordering and grid convergence.

  1. Name the inputs and units that the atoms and solids model needs.
  2. Separate the state you must keep from values you can calculate when needed.
  3. Write one rule that maps the current state and inputs to an observable result.
  4. Choose a limiting case, unit check, invariant, or known result before trusting an output.
  5. State one assumption you would change before using this simplified model for a real decision.

Share to: