MétaCan
Menu
Back to cohort
Record W2801971004 · doi:10.4271/2018-01-0874

Development and Calibration of One Dimensional Engine Model for Hardware-In-The-Loop Applications

2018· article· en· W2801971004 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 · 2018
Typearticle
Languageen
FieldEngineering
TopicReal-time simulation and control systems
Canadian institutionsUniversity of Toronto
Fundersnot available
KeywordsCalibrationLoop (graph theory)Computer scienceDevelopment (topology)Hardware-in-the-loop simulationControl engineeringComputer hardwareEmbedded systemEngineeringPhysicsMathematics

Abstract

fetched live from OpenAlex

<div class="section abstract"><div class="htmlview paragraph">The present paper aims at developing an innovative procedure to create a one-dimensional (1D) real-time capable simulation model for a heavy-duty diesel engine. The novelty of this approach is the use of the top-level engine configuration, test cell measurement data, and manufacturer maps as opposite to common practice of utilizing a detailed 1D engine model. The objective is to facilitate effective model adjustments and hence further increase the application of Hardware-in-the-Loop (HiL) simulations in powertrain development. This work describes the development of Fast Running Model (FRM) in GT-SUITE simulation software. The cylinder and gas-path modeling and calibration are described in detail. The results for engine performance and exhaust emissions produced satisfactory agreement with both steady-state and transient experimental data. Therefore, the presented methodology shows a great potential for testing and validation of new control strategies in Engine Management System (EMS) and for optimizing engine performance using HiL systems. The model has been successfully used in powertrain testing and calibration in the <u>VIR</u>tual <u>TE</u>st <u>C</u>ell (VIRTEC) system at Volvo Penta.</div></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: Bench or experimental · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.969
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.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.017
GPT teacher head0.239
Teacher spread0.222 · 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