Battery lifetime predictions: information leakage from unblinded training

27 March 2023, Version 1
This content is a preprint and has not undergone peer review at the time of posting.

Abstract

Data-driven models are being developed to predict battery lifetime because of their ability to capture complex aging phenomena. In this perspective, we demonstrate that it is critical to consider the use cases when developing prediction models. Specifically, model features need to be classified to di↵erentiate whether or not they encode cycling conditions, which are sometimes used to artificially increase the diversity in battery lifetime. Many use cases require the prediction of cell- to-cell variability between identically cycled cells, such as production quality control. Developing models for such prediction tasks thus requires features that are blind to cycling conditions. Using the dataset published by Severson et al. in 2019 as an example, we show that features encoding cycling conditions boost model accuracy because they predict the protocol-to-protocol variability. However, models based on these features are less transferable when deployed on identically cycled cells. Our analysis underscores the concept of using the right features for the right prediction task. We encourage researchers to consider the usage scenarios they are developing models for, and whether or not to blind their model from information on cycling conditions in order to avoid information leakage. Equally important, benchmarking model performance should be carried out between models developed for the same use case.

Keywords

Lithium-ion battery
lifetime prediction
machine learning
data leakage
feature engineering

Supplementary materials

Title
Description
Actions
Title
Supplemental Information
Description
Supplemental material for the perspective article "Battery lifetime predictions: information leakage from unblinded training"
Actions

Comments

Comments are not moderated before they are posted, but they can be removed by the site moderators if they are found to be in contravention of our Commenting Policy [opens in a new tab] - please read this policy before you post. Comments should be used for scholarly discussion of the content in question. You can find more information about how to use the commenting feature here [opens in a new tab] .
This site is protected by reCAPTCHA and the Google Privacy Policy [opens in a new tab] and Terms of Service [opens in a new tab] apply.