MétaCan
Menu
Back to cohort
Record W2280044801 · doi:10.4271/2006-01-0114

Using Real-Time Simulation in Hybrid Electric Drive and Power Electronics Development: Process, Problems and Solutions

2006· article· en· W2280044801 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

VenueSAE technical papers on CD-ROM/SAE technical paper series · 2006
Typearticle
Languageen
FieldEngineering
TopicReal-time simulation and control systems
Canadian institutionsOpal-Rt Technologies (Canada)
Fundersnot available
KeywordsPower electronicsProcess (computing)ElectronicsComputer scienceControl engineeringElectrical engineeringEngineeringVoltage

Abstract

fetched live from OpenAlex

<div class="htmlview paragraph">This paper highlights the usage of real-time simulation in the development process of hybrid electric drive and other vehicle components that make use of power electronics. The paper objective is to demonstrate the various usages of real-time simulation technologies in the V-cycle design process of hybrid vehicle named Faster-Than-Real-Time (FTRT), Rapid Control Prototyping (RCP) and Hardware-In-the-Loop (HIL). The paper explains these solutions in the context of design of fuel cell hybrid electric vehicle systems and power converters.</div> <div class="htmlview paragraph">The paper shows that the fast dynamic of electric systems requires powerful real-time simulators as well as adapted solvers and simulation techniques. Special models are required to accurately simulate in real-time the power converter and drives found in hybrid electric vehicles.</div> <div class="htmlview paragraph">The paper demonstrates this by the use of basic examples followed by the real-time simulation of a fuel cell hybrid vehicle (FCHV). The FCHV case makes use of the two main applications of real-time simulation technologies, RCP and HIL simulation, interconnected in a complete fuel cell hybrid vehicle application.</div>

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: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.986
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0000.000
Research integrity0.0000.001
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.009
GPT teacher head0.225
Teacher spread0.216 · 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