Optimal Control
Optimal control designs a control protocol by optimizing a stated objective subject to physical and numerical constraints. In quantum mechanics the controls may be microwave amplitudes, laser phases, magnetic fields, tunneling amplitudes, detunings, dissipative couplings, or measurement-based feedback laws. In open systems, the target must be balanced against decoherence, leakage, bandwidth, calibration uncertainty, and model error.
The key idea is not “let an optimizer find a pulse.” The key idea is:
state the dynamical model, the allowed controls, the objective,the constraints, and the validation tests before trusting the pulseFor a reproducible small-scale numerical contract, see Optimal Control Toy Problems. This page explains the concepts that such a notebook should make explicit. For processor-facing method selection, including CRAB, black-box search, reinforcement learning, hardware query budgets, pulse deployment, and release evidence, see Optimal Control for Quantum Processors.
Control Problem
Section titled “Control Problem”A typical open-system control model has
where denotes one or more control waveforms. For a driven Markovian model,
The optimization chooses from an allowed class. The class matters: a piecewise-constant waveform, a Fourier series, a spline, a Gaussian pulse family, and an arbitrary point-by-point waveform are different optimization problems.
The control problem is incomplete until it specifies:
- initial states or input channels;
- target state, unitary, channel, observable, or steady state;
- final time or allowed duration;
- amplitude, bandwidth, smoothness, phase, and energy constraints;
- known noise and uncertainty parameters;
- objective function and penalty terms;
- solver tolerances and validation tests.
Objectives
Section titled “Objectives”An objective function turns the physics goal into a number. Since many optimizers minimize, it is common to write
where is a physical fidelity or success score, penalizes control cost or roughness, and penalizes lack of robustness. The weights and are modeling choices, not constants of nature.
Common targets include:
| Target | Example score |
|---|---|
| state preparation | |
| population transfer | |
| unitary gate | average gate fidelity or process fidelity |
| channel synthesis | distance between Choi matrices or action on a test set |
| cooling | final occupation or energy |
| steady-state engineering | distance to target fixed point plus Liouvillian gap checks |
| sensing protocol | Fisher information, contrast, or signal-to-noise objective |
State-transfer objectives can be useful for calibration, but they do not certify a gate. A pulse that maps one initial state correctly may act badly on another input state. Gate or channel objectives must test the action on a basis of states, a process representation, or an equivalent fidelity formula.
Constraints Are Physics
Section titled “Constraints Are Physics”Constraints are not cosmetic. They are part of the model.
| Constraint | Why it matters |
|---|---|
| amplitude bound | prevents unphysical instantaneous rotations or heating |
| finite bandwidth | models electronics, optics, filters, and pulse shaping |
| smoothness | reduces spectral leakage and calibration sensitivity |
| duration | trades speed against decoherence and adiabaticity |
| leakage penalty | discourages population outside the computational subspace |
| detuning uncertainty | tests robustness to calibration drift |
| noise model | prevents optimizing a closed-system fantasy |
| hardware transfer function | maps programmed waveform to delivered waveform |
Without constraints, an optimizer can exploit features not present in the apparatus. A pulse that requires arbitrarily sharp edges or enormous amplitudes is a mathematical artifact unless the hardware can deliver it and the model remains valid at those scales.
Open-System Objectives
Section titled “Open-System Objectives”For a Markovian density-matrix model, the final state is
where is a completely positive trace-preserving map when the model is valid. If the target is a unitary gate , the open-system result is generally not unitary; it is a channel. Comparing only one input state can hide amplitude damping, dephasing, leakage, and nonunital drift.
A simple gate-style score averages over a set of input states:
This is not the only fidelity convention, but it is transparent and reproducible. More formal process fidelities should state the Choi-matrix normalization, basis ordering, and whether leakage is included or postselected.
Gradients and Adjoints
Section titled “Gradients and Adjoints”For many controls, the waveform is discretized into time slices:
Gradient methods compute how the objective changes when each changes. In open-system notation, an adjoint-state expression has the schematic form
Here is a forward-propagated state, is a backward-propagated costate, and is the time-slice propagator. The exact formula depends on the fidelity, discretization, and inner-product convention.
GRAPE-style methods use this forward-backward structure efficiently for piecewise controls. Krotov methods update controls using a related variational construction designed to give monotonic improvement under suitable assumptions. Automatic differentiation can also compute gradients, but it does not remove the need to define the physics and validation tests.
GRAPE and Krotov Preview
Section titled “GRAPE and Krotov Preview”GRAPE, gradient ascent pulse engineering, is widely used when controls are piecewise constant and the objective gradient can be evaluated slice by slice. It is especially natural for finite-dimensional Hamiltonian control and has open-system extensions using Liouvillian propagators.
Krotov methods frame the update as an optimal-control variational problem with forward and backward propagation. They are often used when one wants monotonic improvement guarantees under the assumptions of the method.
Both families are algorithms for a chosen mathematical problem. Neither guarantees that the optimized pulse is physically robust, experimentally deliverable, or globally optimal.
Robust Optimization
Section titled “Robust Optimization”A pulse optimized for a single parameter set may fail when the detuning, coupling, noise rate, or calibration shifts. Robust control replaces a single score by an ensemble score, for example
where labels sampled parameter values and are weights. The pulse is then rewarded for working across the ensemble.
Robustness should be tested on parameter values not used during optimization. Otherwise the pulse may simply overfit the training grid.
Validation Workflow
Section titled “Validation Workflow”A trustworthy optimal-control result should report:
- the model Hamiltonian, dissipators, and frame convention;
- the control parametrization and bounds;
- the objective and all penalty weights;
- the time grid and propagation tolerances;
- the optimizer and stopping criteria;
- the initial guesses or random seed;
- a simple baseline pulse for comparison;
- physical fidelity separate from penalized objective;
- robustness sweeps over noise and detuning;
- leakage and constraint violations;
- enough metadata for reproduction.
For density-matrix simulations, Solving Lindblad Equations gives the numerical cautionary background. For the small qubit-control benchmark, use Optimal Control Toy Problems.
Relation to Other Control Strategies
Section titled “Relation to Other Control Strategies”Optimal control is not a replacement for analytic pulse design. It is a way to search a larger control space once the target and constraints are clear.
Rabi and Ramsey Control supplies the basic calibration primitives. Pulse Sequences collects standard hand-designed patterns. Dynamical Decoupling explains noise filtering by pulse timing. Measurement-Based Feedback designs controls that depend on a live record. Reservoir Engineering changes the dissipative dynamics rather than merely shaping Hamiltonian drives, and Dissipative State Preparation focuses on target steady states.
Optimal control can combine these ideas: optimize a shaped pulse, optimize an echo-like timing pattern, or optimize both Hamiltonian and dissipative resources. The result still needs independent validation.
Common Mistakes
Section titled “Common Mistakes”- Optimizing a closed-system model and reporting the result as open-system control.
- Reporting the penalized objective without the physical fidelity .
- Treating a state-transfer score as a gate fidelity.
- Ignoring amplitude, bandwidth, smoothness, and leakage constraints.
- Comparing optimized pulses to no baseline pulse.
- Trusting improvements smaller than solver tolerance or model uncertainty.
- Optimizing on the same parameter grid used for robustness claims.
- Hiding failed initial guesses, local traps, or sensitivity to random seed.
- Forgetting that an experimentally delivered waveform may differ from the programmed waveform.
Exercises
Section titled “Exercises”State transfer is not a gate
Section titled “State transfer is not a gate”A pulse maps to with high fidelity. Why does this not prove it implements an gate?
Solution
A gate is a map on all input states, not one state. The same pulse might map correctly while adding the wrong phase to , dephasing superpositions, leaking population, or acting nonlinearly after postselection. To certify a gate, one must test a process representation, an average gate fidelity, or enough input states to determine the channel within the intended model.
Penalized objective
Section titled “Penalized objective”Suppose two pulses have physical fidelities and . Pulse B is much smoother, so an objective assigns . Which pulse is “better”?
Solution
Neither is universally better without the design goal. Pulse A has higher physical fidelity in the model. Pulse B has lower penalized objective because smoothness was rewarded. If smoothness represents a real hardware constraint or robustness requirement, B may be preferred. The result should report both and so readers can see the tradeoff.
Robust objective
Section titled “Robust objective”A pulse is optimized at detuning and works poorly at . Write a simple robust objective using three detunings.
Solution
One simple choice is an equally weighted infidelity average:
Equivalently,
The optimized pulse should then be tested at additional detunings not included in the three-point training set.
Cross-Links
Section titled “Cross-Links”- Driven Open Systems
- Rabi and Ramsey Control
- Control, Readout, and Calibration
- Pulse-Level Control
- Optimal Control for Quantum Processors
- Quantum Control in AMO
- Pulse Sequences
- STIRAP
- Effective Hamiltonians in Quantum Information
- Dynamical Decoupling
- Measurement-Based Feedback
- Reservoir Engineering
- Dissipative State Preparation
- Lindblad–GKSL Equation
- Steady States and Relaxation
- Noise Spectra
- Solving Lindblad Equations
- Optimal Control Toy Problems
- Approximation Checklist
- Reading List
References
Section titled “References”- C. Brif, R. Chakrabarti, and H. Rabitz, “Control of quantum phenomena: past, present and future,” New Journal of Physics 12, 075008 (2010).
- D. D’Alessandro, Introduction to Quantum Control and Dynamics, Chapman and Hall/CRC (2007).
- N. Khaneja, T. Reiss, C. Kehlet, T. Schulte-Herbrüggen, and S. J. Glaser, “Optimal control of coupled spin dynamics: design of NMR pulse sequences by gradient ascent algorithms,” Journal of Magnetic Resonance 172, 296–305 (2005).
- S. J. Glaser, U. Boscain, T. Calarco, C. P. Koch, W. Kockenberger, R. Kosloff, I. Kuprov, B. Luy, S. Schirmer, T. Schulte-Herbrüggen, D. Sugny, and F. K. Wilhelm, “Training Schrödinger’s cat: quantum optimal control,” European Physical Journal D 69, 279 (2015).
- V. F. Krotov, Global Methods in Optimal Control Theory, Marcel Dekker (1996).
- T. Schulte-Herbrüggen, A. Spörl, N. Khaneja, and S. J. Glaser, “Optimal control for generating quantum gates in open dissipative systems,” Journal of Physics B 44, 154013 (2011).
Frontier Context
Section titled “Frontier Context”Molecular Control Frontiers tracks current evidence for hardware-aware pulse optimization, transfer between instruments, molecular wavepacket steering, and product-selective control. The objective functions, adjoint methods, constraints, robustness ensembles, and validation principles developed here remain canonical.