Appearance
Snapshots
A snapshot is the complete state of a running simulation at one moment. Later runs can start from that moment instead of from 0 s, so a circuit that needs 10 s to settle reaches steady state once, and every fault study after that only simulates what comes after.
Not available yet
Snapshots are still in development and aren't part of any plan yet, so the menu entry stays hidden outside a development build. The command-line tool can already save and resume snapshots (see below).
Record a snapshot
Open the menu in the top bar and choose Snapshot, then Record snapshot.
The time defaults to the current Duration, in the same unit. The run starts from 0 s and stops at the time you enter, then saves. A time longer than Duration runs past it. If you press Stop before that time, or the run fails, nothing is saved and the logs say why.
A circuit keeps one snapshot. Recording again replaces it. The new snapshot is saved but not loaded: nothing appears next to Run until you load it. If a snapshot was already loaded, a successful recording takes that chip off. Stopping early leaves the loaded snapshot as it was.
Where the snapshot is kept depends on the circuit:
- A cloud document you own keeps its snapshot with the document. Deleting the document deletes the snapshot.
- The local circuit (one you haven't saved to the cloud) keeps it in this browser. Replacing the local circuit (New, opening a file, an import) removes it.
- Samples and documents shared with you don't keep snapshots.
Load a snapshot
In the Snapshot dialog, Load snapshot puts a chip next to Run. The chip reads "From 10 s" (the snapshot time). Opening a circuit does not load a saved snapshot on its own. While the chip is on, Run starts from the snapshot:
- Duration is still the end time, counted from 0 s. A snapshot at 10 s with a duration of 12 s simulates the last 2 s.
- The displays show only the resumed part, so their time axes start just after the snapshot time.
Click the chip to open its details: the snapshot time, the end time, and any values you changed since the snapshot. From there you can:
- turn Start from the snapshot off to run from 0 s again (the chip then reads From 0 s; the snapshot stays loaded),
- Unload it, which takes the chip off and leaves the snapshot saved.
The Snapshot dialog also does this:
- Load snapshot puts the chip back after an unload.
- Unload snapshot takes the chip off without deleting the snapshot.
- Download saves a
.numasnapfile, for the command-line tool or another machine. - Delete snapshot removes it, after a confirmation.
What you can change before resuming
A snapshot belongs to the circuit as it was when it was saved. You can still change the timing and values of events that happen after the snapshot:
| Component | Values you can change |
|---|---|
| Fault (1-phase) | Fault resistance, trigger time, clear time |
| Fault (3-phase) | Fault resistance, trigger time, fault duration |
| Breaker, Breaker (3-phase) | Trigger times |
| PQ Load (3-phase) | Breaker times |
| Signal Generator | Start time, ramp time, pulse width |
| Time Table Source | The table |
Run refuses to start from the snapshot, and tells you why, when:
- the duration ends at or before the snapshot time,
- the time step differs from the snapshot's,
- a component was added, removed or rewired, or any other value changed,
- a changed event time falls before the snapshot time,
- the snapshot was written by a version of NumaSim whose components this version can't read.
Turn Start from the snapshot off, or unload the snapshot, to run from 0 s instead.
Engine
Snapshots run on the browser engine. The cloud engine doesn't support them yet, so a run that saves or resumes a snapshot on it is refused with a message asking you to switch engines.
Command line
The numasim command-line tool can save and resume the same snapshot files:
sh
numasim simulate circuit.numasim.json --save-state-at 10 --save-state base.numasnap
numasim simulate circuit.numasim.json --load-state base.numasnap--save-state-at also accepts end. A resumed run continues from the snapshot time to the document's duration.
See also
- Running a simulation — the run controls, progress and logs.
- Load flow — another way to shorten the settling part of a run.