Skip to content

QubitWire / Self-directed portfolio project

QuTiP pathway: distinguish numerical convergence from a good physical model

Produce a dynamics notebook that tests its numerical answer and explains its physical assumptions.

Reviewed

Starting skills
Python, differential equations, basic quantum dynamics
Portfolio output
Convergence table plus physical-assumption note
A useful completion check
Observable stable under justified numerical refinement; modelling limitations stated
Hardware needed
No
Release boundary
Distinguish stable and latest documentation branches

QuTiP’s current documentation provides solvers for closed and open quantum-system dynamics, including master-equation methods and configurable numerical options. This pathway uses a small driven system to practise a distinction essential to scientific software work: a numerically stable answer can still come from an inappropriate physical model. The project therefore has two separate reviews, one for the computation and one for the assumptions. It is a resource pathway, with no current vacancy, laboratory access or experimental result claimed.

Choose a model with an independently understandable limiting case. Set out the Hamiltonian, initial state, measured observables and any dissipation terms, with units and conventions explicit. First run a parameter regime in which a simple analytical expectation or a conservation property can be checked. Then introduce one additional physical effect. The notebook should explain why that effect belongs in the model rather than adding terms only because a solver accepts them. A reviewer should be able to connect every parameter to a stated modelling assumption.

The numerical review varies solver tolerances, time resolution where relevant and basis truncation if the system uses an infinite-dimensional degree of freedom. Compare the observable of interest under these changes and define a convergence criterion before selecting the final settings. A smooth-looking curve is not sufficient evidence. The result can be stable at displayed resolution while still changing materially when the truncation or solver settings are tightened. Preserve the computational cost so the reader can see the tradeoff between accuracy and resources.

The physical review asks different questions. Does the chosen equation describe the intended interaction with the environment? Are the parameters constant, time dependent or merely illustrative? Which effects have been omitted, and could they change the conclusion? No amount of numerical precision repairs an assumption that does not apply. A useful portfolio discussion presents one example where numerical convergence is achieved but a change in the physical model changes the interpretation. Label both models and avoid claiming that either represents a real device without supporting measurements.

Questions to take with you

Does a smooth plot demonstrate convergence?

No. Convergence requires a controlled change in relevant numerical settings and a stated tolerance for the observable. Visual smoothness alone is not a test.

Why separate two reviews?

The numerical review asks whether the equations were solved reliably. The physical review asks whether those equations are appropriate. Success in one does not guarantee success in the other.

Self-directed project; no vacancy, completed execution, certification or employer endorsement is implied. Pin the software environment before presenting runnable code.

Sources and what they show (2)
  • QuTiP master-equation solver ↗QuTiP project · Latest branch 5.4 observed

    Master-equation and Schrödinger solver roles

    Latest documentation may precede installed stable release; no model validity implied by API availability.

  • QuTiP solver options ↗QuTiP project · Accessed 2026-10-17

    Configurable dynamics-solver parameters

    Choose settings appropriate to pinned release and stated convergence test.

Explore other portfolio projects