MétaCan
Menu
Back to cohort
Record W2013028035 · doi:10.1631/jzus.a071223

An iterative computation method for interpreting and extending an analytical battery model

2007· article· en· W2013028035 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

VenueJournal of Zhejiang University. Science A · 2007
Typearticle
Languageen
FieldEngineering
TopicAdvanced Battery Technologies Research
Canadian institutionsSt. Francis Xavier University
Fundersnot available
KeywordsBattery (electricity)ComputationGRASPProcess (computing)Computer scienceIterative and incremental developmentState of chargePower (physics)Scheduling (production processes)SimulationAlgorithmMathematical optimizationPhysicsMathematics

Abstract

fetched live from OpenAlex

Battery models are of great importance to develop portable computing systems, for whether the design of low power hardware architecture or the design of battery-aware scheduling policies. In this paper, we present a physically justified iterative computing method to illustrate the discharge, recovery and charge process of Li/Li-ion batteries. The discharge and recovery processes correspond well to an existing accurate analytical battery model: R-V-W’s analytical model, and thus interpret this model algorithmically. Our method can also extend R-V-W’s model easily to accommodate the charge process. The work will help the system designers to grasp the characteristics of R-V-W’s battery model and also, enable to predict the battery behavior in the charge process in a uniform way as the discharge process and the recovery process. Experiments are performed to show the accuracy of the extended model by comparing the predicted charge times with those derived from the DUALFOIL simulations. Various profiles with different combinations of battery modes were tested. The experimental results show that the extended battery model preserves high accuracy in predicting the charge behavior.

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.001
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.318
Threshold uncertainty score0.292

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.000
Science and technology studies0.0000.000
Scholarly communication0.0000.002
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.029
GPT teacher head0.366
Teacher spread0.338 · 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