MétaCan
Menu
Back to cohort
Record W2084200394 · doi:10.1177/0037549708097420

Real Time Software-in-the-Loop Simulation for Control Performance Validation

2008· article· en· W2084200394 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.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenueSIMULATION · 2008
Typearticle
Languageen
FieldEngineering
TopicReal-time simulation and control systems
Canadian institutionsWestern UniversityUniversity of Windsor
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsInterfacingSoftwareReal-time simulationAutomotive industryCo-simulationHardware-in-the-loop simulationComputer scienceReal-time Control SystemVehicle dynamicsSimulationControl systemControl engineeringAutomotive engineeringEngineeringControl (management)Computer hardware

Abstract

fetched live from OpenAlex

This paper illustrates an effective real-time software-in-the-loop (SIL) simulation technique for control design performance validation through two case studies in automotive systems: electric power steering (EPS) control and drive control for a switch reluctance motor (SRM) powered by a fuel cell. This technique, if implemented appropriately, will be able to shorten the prototyping time for control system research and development in both academic and industrial areas. The two cases presented involve complicated dynamics: road/tire steering dynamics and chemical/electrical dynamics in a fuel cell, for which software packages are available to simulate. Therefore, for the purpose of steering and SRM drive control performance validation, successful real-time simulation is desired through interfacing with these software, i.e. making software package in the loop. The case studies presented in this paper demonstrate the effectiveness of this concept. The presented real-time SIL simulation is conducted on a two-node computer platform engineered by RT-Lab, operating in fixed-step real time. Comparison between real-time and off-line simulation is also presented.

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 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.192
Threshold uncertainty score0.620

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.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.016
GPT teacher head0.243
Teacher spread0.227 · 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