A hardware control pulse is aimed at an energy gap, so the model first records target and neighbor gaps before asking what responds. The comparison is exact only for the declared gap values and ideal pulse label; real devices add calibration drift, linewidth, crosstalk, pulse-shape error, and spectroscopy uncertainty.

A control pulse is modeled as an exact value compared to exact energy gaps. Exact arithmetic here means exact results for the stated model inputs; measured inputs still carry uncertainty and significant-figure limits.

highlighted = computed this step

Energy gaps are target data

The target gap is 6 while the neighbor gap is 4. The control model keeps those gaps distinct.

ΔEt=6,ΔEn=4\Delta E_t=6,\quad \Delta E_n=4
Two nearby transitionsThe target and neighbor gaps are checked separately.lowhigh6lowhigh4target matchedneighbor off

A pulse is compared to the gaps

A pulse value of 6 is compared against both displayed gaps before a response is shown.

pulse=6\text{pulse}=6
Pulse compared to gapsOnly equality to a gap counts as a match.lowhigh6lowhigh4target matchedneighbor off