MétaCan
Menu
Back to cohort
Record W1967876859 · doi:10.1109/cpre.2010.5469497

Justifying pilot protection on transmission lines

2010· article· en· W1967876859 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

Venuenot available
Typearticle
Languageen
FieldEngineering
TopicPower Systems Fault Detection
Canadian institutionsBC Hydro (Canada)
Fundersnot available
KeywordsTrippingRelayReliability engineeringRedundancy (engineering)Protective relayOvercurrentPower-system protectionEngineeringComputer scienceTelecommunicationsElectric power systemElectrical engineeringCircuit breakerPower (physics)

Abstract

fetched live from OpenAlex

Pilot protection schemes use communication channels to send information from the local relay terminal to the remote relay terminal, thereby allowing high-speed tripping for faults occurring within 100% of the protected line. This document is intended as a tool for protection engineers to assist in determining when pilot protection should be installed for transmission line protection, in addition to a communications independent system. The emphasis is not on which pilot scheme to use, but rather if pilot protection is necessary. (Note: The document does not purport to provide a comprehensive list of all considerations that may be used in making this determination or in determining redundancy requirements.) It is evident that it would be less expensive to only install non-pilot step-distance protection since no communication equipment would be necessary (estimates as high as $150K per terminal for the addition of pilot protection). It is prudent to provide engineering considerations that would aid in justifying the installation and future maintenance costs. This report explores this issue by providing the following: (i) Considerations to determine the need for, and benefits of, pilot protection such as high-speed reclosing, improved system stability and power quality, easier coordination, better resistive coverage, and regulatory issues. (ii) Alternatives to pilot protection and fall back strategies when the channel is lost or degraded, or when temporary configurations are entered. Options include stepped distance, ground inverse time overcurrent, Zone 1 extension, and taking the line out of service. (iii) Considerations to determine pilot system redundancy for a given application depending on the voltage level, regulatory issues and economics, role of voting schemes and redundant channels, dependability vs. security, etc.

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: Bench or experimental · Consensus signal: Bench or experimental
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.595
Threshold uncertainty score0.347

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.021
GPT teacher head0.233
Teacher spread0.213 · 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

Quick stats

Citations17
Published2010
Admission routes1
Has abstractyes

Explore more

Same topicPower Systems Fault DetectionFrench-language works237,207