MétaCan
Menu
Back to cohort
Record W2599928670 · doi:10.1049/iet-gtd.2016.1994

Multi‐objective stochastic optimal power flow considering voltage stability and demand response with significant wind penetration

2017· article· en· W2599928670 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 Generation Transmission & Distribution · 2017
Typearticle
Languageen
FieldEngineering
TopicOptimal Power Flow Distribution
Canadian institutionsÉcole de Technologie Supérieure
Fundersnot available
KeywordsControl theory (sociology)Electric power systemContingencyPower flowWind powerDemand responseVoltageMathematical optimizationComputer scienceAC powerPower (physics)EngineeringMathematicsControl (management)Electricity

Abstract

fetched live from OpenAlex

In this study, a multi‐objective stochastic optimal power flow (SOPF) problem with the presence of uncertain wind power generations is introduced. In particular, this study has two main contributions. First, it proposes a multi‐objective SOPF which consists of the operating cost, voltage stability and emission effects as the objective functions. The wind uncertainty is formulated as a scenario‐based technique. Demand response program is considered in this study, which is one of the most efficient control ways to reduce the risk of voltage instability after a contingency occurrence or a stressed loading condition. In addition, the proposed approach uses the technique of fuzzification to normalise all objective functions and to find the optimal solution. The second contribution proposes a line voltage stability index (LVSI). The proposed LVSI can detect precisely the voltage collapse in comparison with other LVSIs, especially after the occurrence of a given contingency due to the dynamic elements of the system. The proposed multi‐objective SOPF is also carried out with different existing LVSIs as the objective functions. These approaches are tested and validated by the modified WECC test system, the IEEE 39‐bus.

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

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.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.001
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.018
GPT teacher head0.236
Teacher spread0.218 · 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