-
-
Notifications
You must be signed in to change notification settings - Fork 597
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: LLI due to SEI incorrect if loss of active material is enabled #3006
Comments
Related to our earlier discussion of the problem of infinite loops when trying to define the SEI model in terms of concentration: the problem is that the |
In this case, we would use concentration as the basic variables then? Based on that, shall we seperate "SEI concentration on active materials", and "SEI concentration on de-active materials", i.e., similar to the lithium plating model? |
Maybe, but it might make more sense to have a single "SEI concentration" variable and then split proportionally to LAM. Can you share the equations? |
PyBaMM Version
23.4.1
Python Version
3.8.10
Describe the bug
In order to convert SEI thickness into SEI concentration, the surface area to volume ratio a is required. However, if any of the loss of active material models are enabled, a changes over time.
Prior to 15th November 2022, a_typ is used to convert from thickness to concentration. This results in SEI growth being overestimated, with SEI growing on particles that have already been lost.
On 15th November 2022, a_typ was replaced with the time-dependent a(t). However, this is also flawed. If a particle that already had SEI on it is lost, PyBaMM considers that SEI to also be lost, which results in "Loss of lithium due to SEI [mol]" decreasing over time in some cases.
One solution could be to have separate ODEs for the various LLI variables so they are incremented at the point the lithium is lost, but that would be computationally expensive and surely there must be a better way?
Steps to Reproduce
Relevant log output
No response
The text was updated successfully, but these errors were encountered: