MétaCan
Menu
Back to cohort
Record W2338863226 · doi:10.1109/tsg.2015.2472523

Residential Demand Side Management Under High Penetration of Rooftop Photovoltaic Units

2015· article· en· W2338863226 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 Transactions on Smart Grid · 2015
Typearticle
Languageen
FieldEngineering
TopicSmart Grid Energy Management
Canadian institutionsUniversity of British Columbia
Fundersnot available
KeywordsPhotovoltaic systemMathematical optimizationVoltageComputer scienceAutomotive engineeringScheduling (production processes)Peaking power plantEnergy consumptionElectrical engineeringDistributed generationEngineeringRenewable energyMathematics

Abstract

fetched live from OpenAlex

In a residential area where many households have installed rooftop photovoltaic (PV) units, there is a reverse power flow from the households to the substation when the power generation from PV units is larger than the aggregate load of the households. This reverse power flow causes the voltage rise problem. In this paper, we study the use of demand side management to mitigate the voltage rise problem. We propose an autonomous energy consumption scheduling algorithm, which schedules the operation of deferrable loads to jointly shave the peak load and reduce the reverse power flow. The proposed algorithm shifts the operation of deferrable loads from peak consumption hours to hours with high-power generation from the PV units. We use stochastic programming to formulate an energy consumption scheduling problem, which takes into account the uncertainty related to the amount of power generation from PV units. The formulated cost function comprises a monetary cost for energy consumption, the revenue from energy export, and an external cost for the voltage rise. Numerical results show that our proposed algorithm can mitigate the voltage rise problem in areas with high penetration of PV units and reduce the peak-to-average ratio of the aggregate load.

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.880
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.001
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.022
GPT teacher head0.214
Teacher spread0.191 · 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