Appearance
Load flow
NumaSim can solve the steady-state load flow (also called power flow) of your electrical circuit alongside the time-domain simulation. Use it to size a network, check bus voltages under load, or give a transient run a steady operating point to start from.
A load-flow case is a set of buses joined by branches, with generators and loads attached. Each bus is one of three types — a slack bus that sets the reference voltage and angle, a PV bus that holds a scheduled voltage, or a PQ bus that draws fixed real and reactive power:
When to use it
A time-domain simulation answers "what is the voltage at this node right now?". A load-flow solve answers "what is the steady-state voltage at every bus, given the loads and generation specified?". They complement each other:
- Run the load flow first to verify your network is feasible.
- Then run a transient simulation to see how it responds to a disturbance.
Solving a load flow
- Build an electrical circuit with buses, branches, generators, and loads. Place each bus with the Bus tool and set its Type (Slack, PV or PQ) in Bus Properties; see Signal routing & buses. A case needs exactly one slack bus.
- Click Run load flow (⚡) in the top bar. The Load Flow dialog opens and solves straight away with the default settings.
- Read the Solution report: per-bus voltage magnitude and angle, branch flows, slack bus power, and whether the solve converged. Errors and warnings are listed at the top of the dialog; click Locate next to one to highlight the component on the canvas.
- To solve again with other settings, pick a Method (Newton-Raphson, the default, or Fast Decoupled), change the Tolerance (pu) or Max iterations, and click Solve.
The dialog also shows the Input file the solver reads, in a format close to PSS®E raw, so you can check exactly what NumaSim extracted from the canvas.
Under the hood, the default Newton-Raphson solver is iterative: it starts from an initial guess, computes how far each bus is from its scheduled power (the mismatch), solves a linearized update from the Jacobian, applies it, and repeats until the mismatch is within tolerance.
Results on the canvas
After a converged solve, every bus on the canvas shows its voltage and angle, and every generator, load, shunt and branch shows its P + jQ flow with an arrow for the direction. Canvas overlay units in the dialog switches these between Actual (kV, MW, MVAr) and Per-unit. The overlay stays while you move things around and disappears as soon as you change something that affects the load flow.
Starting a transient run from the solution
Every converged solve also writes the solved operating point back into the components that use it — a three-phase source's voltage magnitude and angle, and the setpoints of generator controllers such as exciters and governors — as one step you can undo. The Applied to components table in the dialog lists each value it changed. A transient run started afterwards begins at that operating point instead of settling from an arbitrary start.
Importing PSS®E cases
Coming soon
PSS®E import isn't available yet. New > Import PSS/E… appears in the workspace, greyed out and labelled "Coming soon". This section describes how it will work.
If you already have a network in PSS®E format, the PSS/E Import Wizard brings it in: you choose the files, pick how the records should be modelled, and review everything before anything is created. Open it from your workspace with New > Import PSS/E… (click the NumaSim logo in the editor to get to the workspace). Importing needs a free account.
Files
A load-flow .raw file is required. A dynamics .dyr file is optional; see Dynamic models below.
Modeling options
Two global choices, applied to every record that does not override them in the review table:
- Transmission line model — how each BRANCH record is built. Bergeron travelling-wave and Nominal PI both produce a Transmission Line wired between the two buses, with its data in a line type (see Line types in the status bar, and the line-type library to reuse a type across circuits). Branches with the same data share one type. Bergeron is the default. A Bergeron line whose travel time is shorter than your time step automatically falls back to a nominal-pi section at run time.
- Generator model — whether each GENERATOR record becomes an ideal three-phase Voltage source (the default) or a Synchronous machine. A raw file carries no dynamic data, so machines built from a
.rawalone get the ratings and load-flow schedule from the file with placeholder reactances and inertia.
Reviewing the records
Below the options is one collapsible section per record type — buses, generators, loads, fixed shunts, branches and transformers — showing what the file contains. Each row can be:
- excluded with its checkbox, so it is left out of the import. Dropping a bus drops everything attached to it, and those rows grey out immediately so you can see the knock-on effect before importing.
- edited, for the values that carry physical meaning (generator PG / QG / MBASE, branch R / X / B / rating, load P / Q, transformer R / X / taps). Import stays disabled while any edited cell is not a number.
- overridden, on generator and branch rows, to use a different model from the global choice.
Dynamic models
Attach a .dyr and the wizard gains a Dynamic models section listing each machine, the controllers attached to it, and whether it will reach the canvas. Supported models:
| Kind | PSS®E models | NumaSim component |
|---|---|---|
| Machine | GENROU, GENROE, GENSAL, GENSAE | Synchronous Machine |
| Exciter | IEEET1, ESDC1A | Excitation System (DC1A) |
| Exciter | ESAC4A, EXAC4, SEXS | Excitation System (AC4A) |
| Exciter | ESST1A | Excitation System (ST1A) |
| Exciter | ESAC1A, EXAC1 | Excitation System (AC1A) |
| Governor | TGOV1 | Turbine-Governor (TGOV1) |
| Governor | IEEEG1 (single shaft) | Turbine-Governor (IEEEG1) |
| Governor | HYGOV | Turbine-Governor (HYGOV) |
| Governor | GGOV1 | Turbine-Governor (GGOV1) |
| Stabilizer | IEEEST | Power System Stabilizer (PSS1A) |
| Stabilizer | PSS2B (speed and electrical-power inputs) | Power System Stabilizer (PSS2B) |
| Stabilizer | STAB1 | Power System Stabilizer (STAB1) |
Anything else is listed as unsupported and skipped — the rest of the file still imports. A generator with a machine record is always built as a synchronous machine regardless of the global choice, because dynamics cannot attach to an ideal source.
Controllers are placed next to their machine and wired up for you: terminal voltage and field current into the exciter, field voltage back out, shaft speed into the governor and stabilizer, mechanical torque back out, and the stabilizer's output into the exciter's PSS input. Because the pairing is a real wire, the controllers initialize themselves from the load-flow operating point the same way they would if you had drawn them by hand.
After the import
Import saves the result as a new circuit in your workspace, named after the .raw file, and the wizard reports what it built. Click Open circuit to open it in the editor.
Each imported line is drawn joined: one symbol with a pin at each end, wired straight to its two buses. If the layout leaves a long line stretched across the canvas, right-click it and choose Split line to draw its far end as a separate symbol you can place next to the other bus.
The raw file only carries positive-sequence R, X and B, so the imported line type gets equal positive- and zero-sequence values — the same as saying the phases have no mutual coupling. Edit the type from Line types and enter real zero-sequence data if you plan to study unbalanced faults.
Transformers come in as grounded wye on both sides (YNyn, with each neutral tied to ground inside the transformer); a three-winding unit keeps a delta tertiary. An off-nominal WINDV becomes a Fixed tap on that winding, which holds the ratio for the whole run with no tap signal to wire. Change the connections, or set the tap changer to Variable, in the transformer's properties if your study needs them.