MétaCan
Menu
Back to cohort
Record W2114411845 · doi:10.1109/tpwrd.2008.2002965

Rotary Power-Flow Controller for Dynamic Performance Evaluation—Part II: RPFC Application in a Transmission Corridor

2009· article· en· W2114411845 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.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenueIEEE Transactions on Power Delivery · 2009
Typearticle
Languageen
FieldEngineering
TopicPower System Optimization and Stability
Canadian institutionsHydro-Québec
FundersPolytechnique Montréal
KeywordsMATLABElectric power transmissionControl theory (sociology)Electric power systemController (irrigation)Quadrature boosterEngineeringComputer sciencePower (physics)Electrical engineeringVoltagePhysicsControl (management)Transformer

Abstract

fetched live from OpenAlex

<para xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink"> This paper proposes the performance study of the rotary power-flow controller (RPFC) operating in a two-line transmission corridor. Part I presented the RPFC model and its implementation in SPS/Matlab. This paper presents the simulation results of the RPFC operating in the corridor during the postcontingency period, when one of the two lines is out of service. From the RPFC model and the RPFC control system, derived in part I, this paper first determines the model of the electrical corridor equipped with the RPFC, and then implements the entire model, including the RPFC control system, in the SPS/Matlab. The obtained results provide the behavior of the RPFC as well as that of the corridor during the postcontingency period. This paper analyzes, among other parameters, the influence of the RPST number of poles on the RPFC performances. Finally, the utilization of the RPFC, associated with the shunt capacitive compensation, allows restoring the postcontingency power-flow conditions to be equal to those of the precontingency period. </para>

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: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.893
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.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.009
GPT teacher head0.224
Teacher spread0.216 · 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