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

HVDC grid protection algorithm design in phase and modal domains

2018· article· en· W2810118863 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 · 2018
Typearticle
Languageen
FieldEngineering
TopicHVDC Systems and Fault Protection
Canadian institutionsUniversity of Waterloo
Fundersnot available
KeywordsModalComputer scienceGridAlgorithmMathematicsMaterials scienceGeometry

Abstract

fetched live from OpenAlex

To meet the required operation speed for protection of meshed voltage source converter (VSC) high‐voltage direct current (HVDC) grids, travelling wave‐based algorithms operating in the submillisecond time‐frame can be used. The domain in which these algorithms operate, i.e. modal or phase, determines their performance in fault discrimination, fault type classification, and faulted pole selection. In the recent literature, high‐speed algorithms have been proposed for various VSC HVDC grid configurations and transmission line types; yet, the choice of domain has received insufficient attention. This study offers recommendations for the choice of domain for protection algorithm design of HVDC overhead line or cable systems in symmetric monopolar and bipolar configurations. The theoretical analysis of this study, which is based on fundamental wave propagation theory, indicates that the preferred domain for protection algorithms for cable and overhead line systems are the phase and modal, respectively. Furthermore, the study provides comprehensive guidelines to construct detection functions for both configurations and discusses the errors introduced by approximations. Finally, study results from a bipolar overhead line test system demonstrate the advantages of modal over phase domain for fast fault discrimination and classification and illustrate practical problems associated with non‐ideal detection functions.

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: none
Teacher disagreement score0.822
Threshold uncertainty score0.582

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.023
GPT teacher head0.245
Teacher spread0.222 · 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