MétaCan
Menu
Back to cohort
Record W2345208503 · doi:10.1109/tpwrd.2016.2524654

Automated Review of Distance Relay Settings Adequacy After the Network Topology Changes

2016· article· en· W2345208503 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

aboutThe title or abstract carries a Canadian signal from the geographic lexicon.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueIEEE Transactions on Power Delivery · 2016
Typearticle
Languageen
FieldEngineering
TopicPower Systems Fault Detection
Canadian institutionsnot available
FundersHigh Performance Research Computing, Texas A and M UniversityAdvanced Research Projects Agency - EnergyDefense Advanced Research Projects AgencyU.S. Department of Energy
KeywordsRelayNetwork topologyTopology (electrical circuits)Computer scienceProtective relayComputer networkElectrical engineeringEngineeringPhysicsPower (physics)

Abstract

fetched live from OpenAlex

A challenge raised in today's power system is assessing the system protection security and dependability after the topology has been changed due to relay operation upon the occurrence of cascading faults or intentional operator switching action. This paper proposes an automated setting calculation module which could be used to review the adequacy of the distance relay settings following network topology changes. The calculation procedure is broken down into blocks which could be processed in parallel in order to improve the computation speed. A new concept called distance of impact is proposed to reduce the computational burden by conducting the calculations on a limited portion of the network affected by the topology change. The module performance is tested on a synthetic IEEE 118-bus and real-life Alberta transmission operator systems. A sensitivity analysis in the form of N-2 contingency impact on the network relay settings coordination is conducted on the test systems.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.968
Threshold uncertainty score0.519

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.006
GPT teacher head0.214
Teacher spread0.208 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it