Expand description
PSS/E monitored element files (.mon).
A .mon file names what a contingency analysis reports on: branch flows,
interface flows, and bus voltages. Every scope that names a subsystem is
resolved against a .sub file’s SubsystemSet.
MONITOR VOLTAGE RANGE SUBSYSTEM 'ILLINOIS200' 0.950 1.050
MONITOR BRANCHES IN SUBSYSTEM 'ILLINOIS200'
MONITOR TIES FROM SUBSYSTEM 'ILLINOIS200'
ENDMonitoredSet::parse reads UTF-8 text and touches no filesystem.
Statements outside the grammar keep their trimmed line and are reported.
MonitoredSet::to_mon writes the set back in one canonical spelling, and
MonitoredSet::resolve binds it to the rows of a BalancedNetwork.
The grammar, its evidence, and the writer’s spellings are in FORMAT.md
next to this file.
Structs§
- Branch
Ref - One branch named by its terminal buses and circuit id.
- Interface
Member - One branch of an interface, and how the statement stated it against the stored row.
- Monitored
Parsed - Output of a tolerant monitored element read.
- Monitored
Resolution - What a whole monitored element set bound to. Rows are positions in the tables of the network the set was resolved against.
- Monitored
Set - One monitored element file.
- Resolved
Interface - One interface and the branches its flow sums over.
- Resolved
Voltage Scope - One voltage statement’s buses and limits.
highis absent for a deviation statement that names one value. - Unresolved
Monitor - One statement that named nothing, kept with the reason.
Enums§
- Monitor
Scope - The buses a voltage statement applies to.
- Monitor
Statement - One monitor statement.
- Unresolved
Monitor Reason - Why a monitor statement named nothing.