Anticipating contingengies in power grids using fast neural net screening

Source

Publication And Credibility

  • Paper date: 2018-05-03.
  • Venue/status: IJCNN 2018; arXiv preprint available.
  • Credibility: Historical RTE/ChaLearn source cited by L2RPN; older than one year and used for contingency-screening lineage.

Core Claim

The paper screens contingencies with neural networks to prioritize expensive power-flow analyses.

L2RPN / Grid2Op Notes

It treats line disconnections and related contingencies as rare but operationally important exogenous events that should not be erased by average-case models.

Action-Time-Series Notes

This source is useful when Grid2Op is treated as an action-conditioned graph time-series environment:

power-grid observations + topology / redispatch / storage control input + scenario context
  -> next grid observations + safety/cost outcome

The terminology distinction matters. Topology changes, redispatching, curtailment, and storage commands are actions or control inputs when an agent chooses them. Line failures, maintenance outages, weather-driven renewable shifts, and demand variation are events or exogenous variables unless they are deliberately controlled by the experimenter.

Foundation TSFM Relevance

Agenda slotVerdictEvidenceMissing pieces
Causal structure, counterfactuals, and controladjacentGood evidence for rare-event preservation in power-grid time-series modeling, with line disconnections treated as exogenous contingencies.The task is screening/security analysis rather than controllable action planning or learned candidate-action rollout.
Context interface: topology and channel contextpartially closesPower-grid state is naturally graph-structured and tied to physical assets, limits, and scenario metadata.Needs a reusable schema that a general TSFM can consume across grids and non-grid operational systems.
Benchmark leveladjacentResidual-risk-at-budget and simulator-cost-to-risk-target curves are useful hygiene precedents for rare contingency reports.TSFM-ready comparisons still require pinned environment versions, action sets, reward definitions, and train/test scenario splits.