Inside the simulator

You will learn

What a simulator keeps (state) and what it does not (time between events).

A simulator is state plus a queue of things that happen, and knowing that is what makes its output trustworthy. The lesson's spec, simulator, models the engine itself: states, probe points, trace entries, and the loop that drains events in order. The widget reads the real bench the way a simulator holds state: cables, boards, locks, and the last board runs -- three x7-board runs PASS 51840/51840 -- one command, one snapshot, no narratives between.

Open the interactive lesson →