Skip to content

Observables ​

Observables are the signals a run records. They're what you set up on the canvas before you press Run (see Running a simulation) so the displays have something to draw.

Named signals vs. observables ​

A named signal is any monitored value you've given a name — a node voltage, a branch current, a power, an angle, a controller output. Names live in one flat namespace shared across the whole circuit, and that list of names is what every "pick a signal" box suggests: the Oscilloscope, Plot and Meter signal pickers, and the fields where a component reads a signal by name (the From block, the synchronous machine's rotor-lock gate, and so on).

An observable is a named signal that the simulator also records, so it streams to the displays while the run is in flight. Every named signal is recorded unless you switch its Record box off in the Observables panel (see Tuning what gets recorded). A signal that isn't recorded still exists: it keeps routing its value to any component that reads it by name, and it stays in the signal pickers.

Every named signal is recorded unless you switch its Record box off in the Observables panel. Recorded observables stream to the displays while the run is in flight.

Ways to name a signal ​

  1. Name a wire. Double-click a wire, type a name and press Enter. On an electrical wire the name records the voltage of the node the wire belongs to; on a control wire it records the signal the wire carries. A three-phase wire asks for one name per phase (Phase A, B and C); leave a phase blank to skip it. A named wire works like a GoTo block: a From block can read it by name.
  2. Turn on a component's measurement. Many components can measure something about themselves — a resistor's branch current, a source's active and reactive power, a machine's speed. Open the component's properties dialog, switch the measurement on (for example Measure current → On) and give it a name. That name is the signal's name.
  3. Place a GoTo block on a control signal and fill in its Signal name. See Signal routing & buses.

Monitoring a bus voltage ​

Double-click a bus to open Bus Properties. Under Voltage monitoring there are two independent switches; turn on either, both, or neither:

  • Instantaneous (per-phase node voltage) — one observable per phase, each carrying that phase's instantaneous node voltage. Fill in the Phase A / B / C signal names you care about; a blank phase records nothing.
  • RMS (synthesized magnitude) — a single observable carrying the RMS magnitude of the bus voltage. Choose the Measurement (Line-to-line (LL) or Line-to-Neutral (LN)), the Unit (V, kV, or pu on the bus's V_base) and the RMS signal name.

The RMS switch works by quietly inserting an RMS meter that reads the three phase voltages behind the scenes — you only see the one named RMS observable.

Naming rules ​

  • A name can contain letters, digits, _ and -, and can't start with a digit.
  • Names must be unique across the whole circuit. The editor flags a name that's already taken, and a run with duplicate names is refused.
  • Names live in a single flat namespace shared with From / GoTo signal routing. Pick something descriptive (e.g. v_bus_3 instead of v1) — when your circuit grows past a dozen signals you'll thank yourself.

Tuning what gets recorded ​

Click Observables in the status bar to open the Observables panel. It lists every observable in the circuit with its Name, Kind and Source, and lets you change how each one is recorded:

ColumnWhat it controls
RecordSwitch off to stop recording the signal. It still routes its value and still shows in the pickers.
tStart (s) / tEnd (s)Record only between these simulated times.
DecimKeep every n-th sample, to thin out a long run.
Keep last (s)Keep only the most recent stretch of the run, so a long run doesn't pile up data.

Use Filter by name or source… to narrow the list, select several rows and Apply a value to all of them at once. The settings are saved with the circuit. You can't create an observable from this panel; name a wire or turn on a measurement instead.

What happens when you run ​

When you click Run, every recorded observable streams to the displays that show it, in real time. The data stays on screen until the next run replaces it.

See also ​