MétaCan
Menu
Back to cohort
Record W2909004917 · doi:10.1109/vppc.2018.8604956

Design of a High Performance Battery Pack as a Constraint Satisfaction Problem

2018· article· en· W2909004917 on OpenAlexaff
Louis Pelletier, Félix-Antoine LeBel, Ruben Gonzalez Rubio, M.-A. Roux, João Pedro F. Trovão

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicProduct Development and Customization
Canadian institutionsUniversité de Sherbrooke
Fundersnot available
KeywordsConstraint (computer-aided design)Computer scienceBattery (electricity)Process (computing)Constraint satisfaction problemConstraint satisfactionBattery packCompromiseOrder (exchange)Design processIndustrial engineeringMathematical optimizationEngineeringArtificial intelligenceWork in processPower (physics)Operations managementMathematics

Abstract

fetched live from OpenAlex

This article presents a new framework for battery pack designs of electric vehicles and demonstrates the benefits with a real case study involving an electric motorcycle. The new approach proposes to define the battery pack as a constraint satisfaction problem (CSP). Instead of manually iterating the designs, the automated process gives the designer the freedom to explore the search space completely. By integrating the concept of hard and soft constraints, it helps to steer the search in the right direction. Mostly understanding where the design can be flexible to choose the best compromise. Moreover, by prioritizing the constraints in the right order, execution time can be reduced significantly. Making the process even faster. When applied to a real case scenario, results show that even if the original design was great, opportunities for improvement were still possible. Also, by understanding which constraints were the most important to prioritize, it would have been much easier to see where optimization in the design would have been the most effective.

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 imitation

Not 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.

metaresearch head score (Codex)0.002
metaresearch head score (Gemma)0.003
Version: metacan-v3-hybrid-931329e0061cValidation 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.006
Threshold uncertainty score0.021

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0020.003
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0010.001
Science and technology studies0.0010.001
Scholarly communication0.0020.001
Open science0.0010.001
Research integrity0.0020.001
Insufficient payload (model declined to judge)0.0060.001

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.015
GPT teacher head0.198
Teacher spread0.183 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designSimulation or modeling
Domainnot available
GenreEmpirical

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".

Quick stats

Citations7
Published2018
Admission routes1
Has abstractyes

Explore more

Same topicProduct Development and CustomizationFrench-language works237,207