MétaCan
Menu
Back to cohort
Record W2057523769 · doi:10.1049/iet-rpg.2008.0015

Resolving the impact of distributed renewable generation on directional overcurrent relay coordination: a case study

2009· article· en· W2057523769 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 Renewable Power Generation · 2009
Typearticle
Languageen
FieldEngineering
TopicPower Systems Fault Detection
Canadian institutionsWestern University
Fundersnot available
KeywordsOvercurrentRelayFault (geology)MATLABComputer scienceElectric power systemDistributed generationReliability engineeringProtective relayPower-system protectionGrid codeRenewable energyControl engineeringEngineeringControl theory (sociology)Power (physics)AC powerElectrical engineeringCurrent (fluid)Voltage

Abstract

fetched live from OpenAlex

Two approaches are proposed to solve the directional overcurrent relay coordination problem associated with the installation of distributed renewable generation (DRG) in interconnected power delivery systems (IPDS), depending on the existing system protection capability (adaptive or non-adaptive). For adaptive protection systems, the first proposed approach introduces a procedure to select the optimal minimum number of relays, their locations and new settings. This procedure is restricted by the available relay setting groups. For non-adaptive protection systems, the second proposed approach implements a practice to obtain optimal minimum fault current limiter values (FCL) to limit DRG fault currents and restore relay coordination status without altering the original relay settings. An integration of the proposed two approaches is evaluated for IPDSs possessing both protection systems. Three scenarios are assessed for different numbers of DRGs, and DRG and fault locations using an optimisation model implemented in GAMS software and a developed MatLab code. The obtained results are reported and discussed.

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.001
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: Empirical
Teacher disagreement score0.081
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
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.023
GPT teacher head0.282
Teacher spread0.259 · 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