MétaCan
Menu
Back to cohort
Record W2078013272 · doi:10.1109/tdc.2006.1668602

Impact of Transformer Inrush Currents on Sensitive Protection Functions

2006· article· en· W2078013272 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
TopicNon-Destructive Testing Techniques
Canadian institutionsGeneral Electric (Canada)
Fundersnot available
KeywordsInrush currentTransformerElectrical engineeringEnvironmental scienceComputer scienceReliability engineeringVoltageEngineering

Abstract

fetched live from OpenAlex

Transformer inrush currents are known to cause problems for sensitive protection functions applied to a power transformer itself, or in a near vicinity of a transformer. Magnetizing inrush currents contain significant and slowly decaying dc components. This makes Ct saturation plausible and causes more problems for associated protection. Sensitive protection functions that respond to currents are affected most. This paper reviews impact of transformer inrush currents on five protection function: (i) main differential function of the transformer, (ii) restricted earth fault protection, (iii) stator differential protection for generators, (iv) sensitive ground directional overcurrent functions used for line and feeder protection, and (v) distance protection. For each of the covered protection functions the problem is reviewed and quantified, and practical solutions presented

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: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.556
Threshold uncertainty score0.378

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.015
GPT teacher head0.251
Teacher spread0.237 · 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

Citations13
Published2006
Admission routes1
Has abstractyes

Explore more

Same topicNon-Destructive Testing TechniquesFrench-language works237,207