Efficiency analysis of hybrid electric vehicle (HEV) traction motor-inverter drive for varied driving load demands
Bibliographic record
Abstract
It is a well-understood fact that power electronic converters and electric propulsion motors are extremely critical for every hybrid electric vehicle (HEV) system. It is essential that the traction motor must meet demands of varied driving schedules, and at the same time, it should run at its most optimal operating points to achieve higher drive train efficiency. Therefore, modeling the motor-inverter losses/efficiencies over typical city and highway driving schedules is the key to observe and analyze practical drive train efficiency and vehicle performance. Considered as a “black box,” the motor-inverter functions as an energy conversion block. It provides known outputs when certain inputs are applied. In this paper, a detailed efficiency analysis of a typical traction motor-inverter drive system, more specific to a parallel HEV, is presented. The HEV system is tested over a range of different driving load demands, which include 3 stop-and-go type low-speed driving patterns and 3 high-speed driving patterns. The motor-inverter efficiency analysis is carried out based on the resulting efficiency map data. The Advanced Vehicle Simulator (ADVISOR) software is used for modeling and simulation purpose. Efficiencies under both motoring mode and regenerative braking mode are monitored and summarized.
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".