Issue 1245 active material - #1262
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #1262 +/- ##
===========================================
+ Coverage 98.06% 98.07% +0.01%
===========================================
Files 265 270 +5
Lines 14900 15030 +130
===========================================
+ Hits 14611 14741 +130
Misses 289 289
Continue to review full report at Codecov.
|
| return pybamm.FunctionParameter( | ||
| "Negative electrode surface area to volume ratio [m-1]", inputs | ||
| ) | ||
| def epsilon_s_n(self, x): |
There was a problem hiding this comment.
If you set a model for LAM then the variable corresponding to epsislon_s_n and the parameter epsilon_s_n will be different (I think?) - the latter will just give the initial parameter value/function provided. Will this cause confusion? What you really provide as a parameter is the initial active material volume fraction, but I think it would be messy to append "Initial" everywhere. The same is true for porosity.
I don't think this needs changing here, but something to think about in the future. I think my opinion is to leave it as is, and that it is understood that if you have a model describing how a parameter changes then that parameter should be treated as a variable.
There was a problem hiding this comment.
Yes, this is something we should mention when we put together the workflow for degradation modeling. I agree putting "Initial" into the parameter names would be messy
|
Hi, I have made a loss of active material submodel in pybamm. It is based on the LAM model (Eq. 25) in Reniers et al. Would you mind if I push it here? |
|
Yes, go for it! This branch has now been merged though so you'll need to open a PR to develop |
|
I see there is a place holder already, but my implementation is not based on this. How do you think is the best way to do? Is it good to push my current version (tracing back to the last commit on Nov 17, 2020) to develop anyway? |
Description
Set up active material models ready to model loss of active material
Fixes #1245
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 docsand then$ make clean; make htmlYou can run all three at once, using
$ python run-tests.py --quick.Further checks: