MétaCan
Menu
Back to cohort
Record W2971889244 · doi:10.1109/tpel.2019.2939301

Active Saturation Mitigation in High-Density Dual-Active-Bridge DC–DC Converter for On-Board EV Charger Applications

2019· article· en· W2971889244 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

VenueIEEE Transactions on Power Electronics · 2019
Typearticle
Languageen
FieldEngineering
TopicAdvanced DC-DC Converters
Canadian institutionsUniversity of Toronto
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsConvertersDuty cycleElectrical engineeringTransformerForward converterBattery chargerElectronic engineeringEngineeringBuck converterVoltageComputer scienceBoost converterPhysicsBattery (electricity)

Abstract

fetched live from OpenAlex

This article presents a transformer saturation prevention algorithm (SPA) targeting dual-active-bridge (DAB) dc-dc converters utilized in bidirectional, two-stage electric vehicle (EV) on-board battery chargers. Saturation prevention is achieved by detecting the variation in transformer current slope near the boundary of saturation and applying duty-cycle offsets to the DAB converter full bridges. Compared to alternative methods of saturation mitigation, the proposed algorithm offers the following benefits: Lower transformer design safety margins which enable volume reduction with minimal harm to efficiency, and low-cost implementation using a single low-cost current sensor even at high converter switching speeds. Experiments on a custom 6.6-kW on-board EV charger confirm the controller functionality and initial converter analysis. A peak converter efficiency of 96.8% with a transformer volume of 80 cm <sup xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">3</sup> is achieved, which is a 50% volume reduction in comparison to other academic works.

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: Bench or experimental
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.786
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.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.006
GPT teacher head0.220
Teacher spread0.214 · 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