MétaCan
Menu
Back to cohort
Record W3120048864 · doi:10.23919/cjee.2020.000028

Flying capacitor design considerations for a 48-to-12 V, 35 a split-phase dickson SC converter

2020· article· en· W3120048864 on OpenAlex
Richard Yue Sun, Samuel Webb, Yan‐Fei Liu

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

VenueChinese Journal of Electrical Engineering · 2020
Typearticle
Languageen
FieldEngineering
TopicAdvanced DC-DC Converters
Canadian institutionsQueen's University
Fundersnot available
KeywordsCapacitorCapacitanceInductorElectrical engineeringConvertersVoltageSwitched capacitorDecoupling capacitorPower (physics)Charge controlEngineeringPhysicsElectrode

Abstract

fetched live from OpenAlex

Switched-capacitor converters can deliver better performance, power density, and switch utilization compared to inductor-based power converters, but they suffer from current spikes during switching due to capacitor charge redistribution. This can be solved by methods such as split-phase control, which was developed to address charge redistribution in Dickson SC converters by controlling the charging and discharging of the circuit's flying capacitors, such that the equivalent branch voltages line up when the circuit switches states. However, split-phase control is most effective at compensating for charge redistribution when all the circuit's flying capacitors are matched in capacitance value. Differences between the capacitance values of the circuit flying capacitors may result in split-phase control not being able to fully compensate for charge redistribution, due to the different charge/discharge rates of the flying capacitors. The work presented in this paper provides an in-depth analysis of the sensitivity of the split-phase Dickson converter to mismatches in flying capacitor values, as well as discussions regarding the design considerations and prototype test results of a split-phase Dickson converter for high-current loads.

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.002
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.907
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.002
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.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.026
GPT teacher head0.255
Teacher spread0.229 · 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