MétaCan
Menu
Back to cohort
Record W2774740500 · doi:10.1109/tia.2017.2670525

Enhancing Power Transformer Differential Protection to Improve Security and Dependability

2017· article· en· W2774740500 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

VenueIEEE Transactions on Industry Applications · 2017
Typearticle
Languageen
FieldEngineering
TopicPower Systems Fault Detection
Canadian institutionsGeneral Electric (Canada)
Fundersnot available
KeywordsDependabilityCurrent transformerDifferential protectionTransformerEngineeringControl theory (sociology)Computer scienceReliability engineeringElectrical engineeringVoltage

Abstract

fetched live from OpenAlex

Current differential principle is a well-known principle used for protection of transformers, motors, generators, buses, and any other type of power equipment with input and output current measurements. Further, the principle is used in developing percent differential protection, which can be programmed to the desired sensitivity for detecting in-zone faults and security during external faults. This protection dependability is usually achieved by modeling a differential-restraining characteristic with two regions, operating and nonoperating, and tracking the real differential restraint ratio during faults. Some external faults with high dc offset and high X/R system time constant would easily saturate the installed current transformers (CTs), which in return would cause high differential/restraint ratio above the preset characteristic into the operating region. In such cases, the differential protection would operate and cause unwanted transformer trip. This paper focuses on some enhancements applied to the differential principle of the main differential protection; it also defines guidance on how to setup the protection for better sensitivity and security. The paper is supported by fault cases, showing the improved security and dependability during internal/external faults with and without CT saturation.

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: Bench or experimental · Consensus signal: Bench or experimental
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.705
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.0010.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.001
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.010
GPT teacher head0.246
Teacher spread0.236 · 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