PSLF workflow
Start with the current case and base power flow. Use network edits and contingencies only after the solved case is credible.
Default tool ladder
open_case(case)solve_case()get_voltage(bus),get_voltage_violations(...), andget_overload_violations(...)to identify the real issue.add_shunt(...),add_generator(...),add_load(...),add_branch(...), oradd_bus(...)for controlled model changes.save_case()after the edited state is worth keeping.run_contingency_analysis()only after the base case is solved and monitored.
Working rules
- Do not run contingencies on an unsolved or obviously bad base case.
- Prefer the smallest corrective action that addresses the violation.
Escalation triggers
Quote the violated bus or branch and its value rather than saying "violations exist".
| Observation | Escalate to |
|---|---|
get_voltage_violations returns low or high buses |
voltage-violation-mitigation |
get_overload_violations returns loaded branches |
thermal-overload-mitigation |
run_contingency_analysis returns binding N-1 cases |
contingency-mitigation |
solve_case fails to converge |
convergence-failure-mitigation |
Deliver
- The case opened and base-case status.
- The key violations found.
- The edits applied and whether the contingency study still fails.