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

Optimal allocation of distributed generation for planning master–slave controlled microgrids

2019· article· en· W2937879615 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 · 2019
Typearticle
Languageen
FieldEngineering
TopicMicrogrid Control and Optimization
Canadian institutionsUniversity of Waterloo
Fundersnot available
KeywordsComputer scienceDistributed generationDistributed computingMaster/slaveMathematical optimizationOperations researchEngineeringElectrical engineeringMathematicsRenewable energyParallel computing

Abstract

fetched live from OpenAlex

This study proposes a novel problem formulation for a planning distributed generation (DG) allocation for microgrids, using the master–slave approach. In the previous planning studies, all DGs have the same operating mode (e.g. operate at unity power factor). For master–slave controlled microgrid, DGs have two possible operating modes: master (non‐unity power factor operation) and slave (unity power factor operation). For planning a master–slave controlled microgrid, in addition to DG siting, the optimal DG operating mode is determined by including a new set of constraints in the planning problem. Thus, the proposed formulation is capable of determining the optimal location of the master and slave DGs with the main objective of minimizing the microgrid's energy losses. The proposed model is formulated as a mixed‐integer non‐linear programming problem; incorporated into an optimal power flow framework and tested on the IEEE 38‐bus systems considering a variable load profile. In addition to this, sensitivity analysis is carried for case studies with different load types and reactive power injection by the slave DGs in the system (e.g. operate at fixed non‐unity power factor). The proposed approach can serve as an efficient tool for utility operators for planning microgrids.

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: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.780
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.016
GPT teacher head0.222
Teacher spread0.206 · 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