Time-series simulation
Hour-by-hour load-flow slices with energy loss, reverse-power hours, storage arbitrage and the LCC evaluation — the heavy study goes through the asynchronous task channel.
Select or create a scheme to open this page
Not computed yet — press Run
Quasi-steady per-timestep power flow: at every time point the load / source injections given by timeSeries.profiles are substituted and the **same** power-flow solver is called (engines/loadflow.js solveLoadflow — the same injection assembly as the existing hourly EMS), each point solved independently; no time-domain recursion between points (stateless)
About the time-series simulation
This page runs the scheme through a day or a longer window instead of a single operating point. The study is studyOptions.enableTimeSeries in engines/time-series.js: for every time point a quasi-steady-state load-flow slice is solved with the same solver the load flow page uses, with only that instant load and source injections rewritten, giving voltage, current and loss sequences plus statistics (maximum loading rate, minimum voltage, loss energy in kWh, and the hours of reverse power flow). A run with more than 24 points, or more than 600 points times busbars, is sent through the asynchronous task channel, and the synchronous path has a hard time gate and returns a partial result marked as such instead of hanging. The storage arbitrage and life-cycle cost card sits on the same page.
A single worst-case operating point hides the cases that actually damage equipment or cost money: the lightly loaded night hours where voltage rises at the end of a long feeder, the midday hours where a PV or storage system pushes power backwards through the transformer, and the accumulated energy lost over a year. The sequences are what make the annual loss energy, the reverse-flow hours and the storage payback defensible, and they are the input to the transformer thermal ageing assessment on its own page.
Input: the list of time points (default 0 to 23, hourly), the hourly active power profile of each load tag, the AC output profile of PV, wind or hydro, the storage charge and discharge profile (positive means charging), the tariff and the storage parameters → chain: for each time point the injections are rewritten by the profile and the same solveLoadflow is called, point by point with no time-domain recursion between points, giving voltage, current, active and reactive power and loss for every node and branch → the points are aggregated into the maximum loading rate, the minimum voltage, the loss energy by integrating the hourly power, and the reverse-power hours where a branch active power is below the threshold → the storage state machine then runs hour by hour under its four constraints and three strategies, feeding the arbitrage and life-cycle cost evaluation → output: the timestamped node and branch sequences, the statistics block, the storage and cost results. Linkage: the load profile sets the loss energy and the minimum voltage; storage charging and discharging change the reverse-flow hours and the transformer loading; the cable section moves the loss energy, which is a direct input to the energy bill and the life-cycle cost; and the PV or wind profile added to the load profile is what creates the reverse flow and the over-voltage, so the source size and the profile have to be read together. Approximations, all disclosed: the model is quasi-steady-state per time slice with no state carried between points and no continuous transient simulation; when no profile is entered the engine uses its built-in industry typical curves, which are engineering typical values; timestamps are hours accumulated from the start and mapped modulo 24 hours onto the daily curve.
Engine study time-series. 24-point runs are synchronous, longer windows return 202 + taskId and are followed up by the card itself (bounded, not a poller).