MétaCan
Menu
Back to cohort
Record W2889287637 · doi:10.1109/jpets.2018.2861559

A Benchmark System for Hardware-in-the-Loop Testing of Distributed Energy Resources

2018· article· en· W2889287637 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 and Energy Technology Systems Journal · 2018
Typearticle
Languageen
FieldEngineering
TopicReal-time simulation and control systems
Canadian institutionsUniversity of AlbertaRTDS Technologies (Canada)
FundersIndian Institute of Technology RoorkeeUniversity of South Carolina
KeywordsBenchmark (surveying)Hardware-in-the-loop simulationElectric power systemController (irrigation)Task (project management)Computer scienceSet (abstract data type)Power (physics)Real-time simulationControl engineeringSimulationEngineeringSystems engineering

Abstract

fetched live from OpenAlex

In order to overcome challenges associated with the integration of distributed energy resources (DER) into state-of-the-art and future power grids, a common basis for testing using appropriate benchmark systems is required. Real-time hardware-in-the-loop (HIL) simulation has proven to be an advanced and efficient tool for the analysis and validation of electric power systems and DER components. However, a common methodology for HIL testing of DER along with the required set of reference systems has not yet been developed. This task-force paper proposes a benchmark system for HIL testing incorporating DER into the real-time simulation environment. A low-voltage benchmark system with detailed HIL setup is proposed for the testing of DER performance. The modeling of DER for real-time applications is discussed, and the detailed laboratory procedures and setups for both controller HIL (CHIL) and power HIL (PHIL) are provided. Results from CHIL simulation related to the centralized controls and experimental results of PHIL simulation related to local control on the benchmark system substantiate the suitability of the proposed real-time simulation approach.

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: Empirical
Teacher disagreement score0.342
Threshold uncertainty score0.645

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.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.008
GPT teacher head0.207
Teacher spread0.199 · 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