MétaCan
Menu
Back to cohort
Record W1971096171 · doi:10.1109/pes.2004.1373143

On composite load modeling for voltage stability and under voltage load shedding

2004· article· en· W1971096171 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 Power Engineering Society General Meeting, 2004. · 2004
Typearticle
Languageen
FieldEngineering
TopicPower System Optimization and Stability
Canadian institutionsJacobs (Canada)
Fundersnot available
KeywordsLoad SheddingVoltageComputer scienceDynamic load testingControl theory (sociology)Voltage regulationAggregate (composite)Stability (learning theory)Reliability engineeringElectric power systemEngineeringControl (management)Power (physics)Structural engineeringElectrical engineering

Abstract

fetched live from OpenAlex

Undervoltage load shedding (UVLS) has been considered by some utilities as a cost-effective corrective tool to overcome voltage instability and abnormal voltage conditions. Load modeling is an important aspect for voltage stability studies and real time system controls pertinent to UVLS. At a given bus, a load would be an aggregate of load elements that would differ in their static and dynamic performance. Also at load centers, aggregate loads would encompass system components of particular characteristics such as load tap changers, SVC's and in-plant generation. Modeling aggregated loads should reflect the nature of load components and fit the applications of the model in studies and real time controls. In a tutorial style, This work discusses the evolution of static and dynamic load models for voltage stability and examines their applicability to UVLS. Load modeling approaches were listed as deterministic, generic and stochastic. Concerns and recommendations were given for adopting one approach or a combination of approaches in aggregate load modeling for UVLS. Load models validation and verification is emphasized especially when using generic or stochastic models.

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.001
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.610
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0010.001
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.012
GPT teacher head0.221
Teacher spread0.209 · 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