MétaCan
Menu
Back to cohort
Record W2559963787 · doi:10.1504/ijhvs.2017.10001857

Optimisation and comparison of different powertrain layouts for parallel hybrid electric vehicles equipped with continuous transmission

2016· article· en· W2559963787 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

VenueInternational Journal of Heavy Vehicle Systems · 2016
Typearticle
Languageen
FieldEngineering
TopicElectric and Hybrid Vehicle Technologies
Canadian institutionsUniversity of Waterloo
Fundersnot available
KeywordsPowertrainContinuously variable transmissionAutomotive engineeringDriving cycleTransmission (telecommunications)Electric vehicleEngineeringAutomatic transmissionFuel efficiencyManual transmissionPower (physics)Sensitivity (control systems)ClutchTorqueElectronic engineeringElectrical engineering

Abstract

fetched live from OpenAlex

The development of an efficient hybrid electric vehicle (HEV) platform needs an optimal design of its powertrain layout. This study is concerned with parallel HEVs (PHEVs) equipped with continuous transmission. First, different types of continuous transmissions, including continuously variable transmission (CVT), power-split CVT (PS-CVT) and multi-fixed ratio PS-CVT (MF-CVT), are discussed and their simulation models are presented. Also, various combinations of these continuous transmissions with PHEV configurations (namely, pre-transmission and post-transmission configurations) are introduced. Then, for a given PHEV model, several powertrain layouts resulting from combining the considered continuous transmissions and PHEV configurations are optimised over a standard drive cycle. The optimised powertrain layouts are compared from different perspectives, for instance the vehicle fuel consumption, emissions and some dynamic performance measures. In particular, the sensitivity of the PHEV performance characteristics to the driving cycle pattern, when it is equipped with each optimised layout, is investigated.

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: Bench or experimental · Consensus signal: Bench or experimental
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.303
Threshold uncertainty score0.389

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.013
GPT teacher head0.251
Teacher spread0.238 · 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