MétaCan
Menu
Back to cohort
Record W3025223055 · doi:10.1049/iet-gtd.2019.1196

Sensitivity factors based transmission network topology control for violation relief

2020· article· en· W3025223055 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.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueIET Generation Transmission & Distribution · 2020
Typearticle
Languageen
FieldEngineering
TopicOptimal Power Flow Distribution
Canadian institutionsIndependent Electricity System Operator
Fundersnot available
KeywordsSensitivity (control systems)Topology (electrical circuits)Network topologyTransmission (telecommunications)Control (management)Computer scienceTransmission networkControl theory (sociology)Computer networkEngineeringElectronic engineeringTelecommunicationsElectrical engineeringArtificial intelligence

Abstract

fetched live from OpenAlex

Transmission networks consist of thousands of branches for large‐scale real power systems. They are built with a high degree of redundancy for reliability concerns. Thus, it is very likely that there exist various network topologies that can deliver continuous power supply to consumers. The optimal transmission network topology could be very different for different system conditions. Transmission network topology control (TNTC) can provide the operator with an additional option to manage network congestion, reduce losses, relieve violation, and achieve cost‐saving. This study examines the benefits of TNTC in reducing post‐contingency overloads that are identified by real‐time contingency analysis (RTCA). The procedure of RTCA with TNTC is presented, and two algorithms are proposed to determine the candidate switching solutions. Both algorithms use available system data: sensitivity factors or shifting factors. The proposed two TNTC approaches are based on the transmission switching distribution factor (TSDF) and flow transfer distribution factor (FTDF), respectively. FTDF‐based TNTC approach is an enhanced version of the TSDF‐based TNTC approach by considering network flow distribution. Numerical simulations demonstrate that both methods can effectively relieve flow violations and FTDF outperforms TSDF.

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 categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.946
Threshold uncertainty score1.000

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.017
GPT teacher head0.226
Teacher spread0.209 · 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