MétaCan
Menu
Back to cohort
Record W1970563958 · doi:10.1109/tpel.2012.2232307

Analysis and Comparison of Frequency Stabilization Loops in Self-Oscillating Current Mode DC–DC Converters

2012· article· en· W1970563958 on OpenAlex
Yue Wen, Olivier Trescases

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

VenueIEEE Transactions on Power Electronics · 2012
Typearticle
Languageen
FieldEngineering
TopicAdvanced DC-DC Converters
Canadian institutionsUniversity of Toronto
Fundersnot available
KeywordsRippleConvertersInductorControl theory (sociology)Phase-locked loopDecoupling (probability)VoltageElectronic engineeringCurrent sensorEngineeringComputer scienceElectrical engineeringControl engineeringPhase noise

Abstract

fetched live from OpenAlex

DC-DC converters, used in bidirectional applications such as battery/u-cap hybrid energy-storage systems, usually operate in current mode with a wide range of input and output voltages. Conventional current-mode control schemes, which requires adaptive slope compensation, are not attractive in these applications. In this paper, a class of self-oscillating hysteretic current-mode control (HCMC) schemes with frequency stabilization are analyzed and compared. Among them, the ripple HCMC scheme has the advantages of the inherent access to the average inductor current information, and inherent decoupling between the voltage and the frequency loops. The modeling and design procedure of two frequency regulation methods, namely the phase-locked loop (PLL) and delay-locked loop (DLL), are presented and compared in detail. The analysis is applicable to a range of inductive converters such as buck, boost, and buck-boost. HCMC implemented with a DLL is shown to not only offer comparable bandwidth compared to the PLL, but is also more robust against system parameter variations. The ripple HCMC controllers with PLL and DLL are implemented digitally, and the two schemes are verified experimentally on a 1 MHz 1-2.5 V to 5 V bidirectional boost converter prototype.

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: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.673
Threshold uncertainty score0.938

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.001
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.009
GPT teacher head0.264
Teacher spread0.255 · 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