MétaCan
Menu
Back to cohort
Record W2343638715 · doi:10.1109/tsg.2015.2496298

Parallel Power Flow on Graphics Processing Units for Concurrent Evaluation of Many Networks

2015· article· en· W2343638715 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
TopicPower System Optimization and Stability
Canadian institutionsRoyal Military College of Canada
Fundersnot available
KeywordsSpeedupComputer scienceGraphics processing unitParallel computingCUDAGraphicsCentral processing unitMassively parallelParallel processingComputational scienceComputer hardware

Abstract

fetched live from OpenAlex

The power flow (PF) analysis provides the steady state of the power system and is key to the simulation of transmission networks. It is a tool commonly used by system operators to visualize the effect of generator settings on the network prior to making a change. In situations involving large networks, hundreds or even thousands of PF analysis may have to be run on the network before finding the optimal power dispatch. This process requires significant computation time and does not allow for rapid control of the network. To address this problem, this paper presents two parallel PF solvers that exploit the massively parallel architecture of graphics processing units (GPU) in a hybrid GPU-central processing unit (CPU) computing environment using compute unified device architecture and OpenMP in order to significantly speedup the concurrent analysis of many instances of a network. Both implementations use sparse matrices, double precision operations, and enforce the reactive power limit of generators. The parallel Gauss-Seidel (G-S) and Newton-Raphson (N-R) PF algorithms are tested on networks ranging from 4 to 2383 buses. The accuracy is validated using MATPOWER and the maximum speedup achieved, compared with a sequential execution on CPU, is 45.2× for G-S and 17.8× for N-R.

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 categoriesnone
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.994
Threshold uncertainty score0.625

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.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.068
GPT teacher head0.282
Teacher spread0.214 · 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