kdjones / lse Goto Github PK

Eventually have to do this...

And searchable by ID. Think the way INetworkDescribable should have been implemented.

Check this box with LNR etc

Create selectable (from a dropdown, etc) measurement validation classes:

Thresholds for voltage and current
Sets of flags for Status Words, etc.

As opposed to complex post-processing, add a concept of a Virtual Measurement that is computed from input measurements to increase observability without changing the solver or post processing. Think the middle node on a tapped line.

The id_co, id_dv, id_st fields of the nd record are not necessarily unique as implied by their name. For example, many external divisions can be named EXT and still be unique. Need to update pattern files.

Create "importable" criteria for when to automatically take a Network Snapshot.

Create an internal status message property for the Network object and have it get updated on events. This way, without knowledge of the inner workings, the UI can see what is going on inside the Network object and report it to the StatusBar.

You need more customized exceptions and null checking. Remember to be a defensive coder - LSE is high availability app.

Create an OutputMeasurement Wrapper Class for all output values. Create a list of references on initialization. Then, "OutputPreparation" will be minimized.

Measurements, Estimates, EnableDisableFlags, BreakerStatus, Switch Status, PerformanceMetrics, TopologyInfo,

Override SwitchingDevice status
Disable Measurements
Disable Equipment
other control parameters
Bit that says control signal is present (i.e. since controller might not always be there)
Create user interface that is an analytic to send these signals.

A way to mark zero-injection buses (since modeling does not require non-zero injection buses to do SE)
Better tapped line processing
Virtual Measurements (already marked in another Issue)

Abstract the interface between the NetworkModel and the matrix building and state computation by implementing a Solver protocol/interface. This way I can implement multiple solvers and then switch between them.

Native compatibility vs translational compatibility.

Subject line. For advanced topology features.

KeyValue == "HistorianID", Value == TimeSeriesValue object