-
-
Notifications
You must be signed in to change notification settings - Fork 572
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
Added new parameter z_sei to allow the user to set SEI valancy #2222
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #2222 +/- ##
========================================
Coverage 99.36% 99.36%
========================================
Files 355 355
Lines 19499 19499
========================================
+ Hits 19375 19376 +1
+ Misses 124 123 -1
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see beta_sei
and beta_plating
being used anywhere
I remember beta_sei being a legacy parameter from when the porosity submodel was an ODE, because I created beta_plating using the same logic. The porosity submodel seems to be ever-changing so is it worth keeping these? |
Let's remove them, it's easy to add back in if needed, and confusing otherwise |
Description
A new parameter "Ratio of lithium moles to SEI moles" (short name z_sei) has been added. This variable was previously hardcoded to 1 for all SEI growth options except "ec reaction limited". As pointed out in issue #2065, z_sei=1 is incorrect for the two most common SEI compoints - LEDC and Li2CO3, both of which require z=2.
The SEI parameter sets have been updated accordingly. The new parameter z_sei is set to 2 by default for all parameter sets except OKane2022, which used the old code for which it was set to 1.
Fixes #2065
Type of change
Please add a line in the relevant section of CHANGELOG.md to document the change (include PR #) - note reverse order of PR #s. If necessary, also add to the list of breaking changes.
Key checklist:
$ flake8
$ python run-tests.py --unit
$ cd docs
and then$ make clean; make html
You can run all three at once, using
$ python run-tests.py --quick
.Further checks: