Skip to content
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

Scaling of interfacial currents with particle shape #1781

Closed
valentinsulzer opened this issue Nov 3, 2021 Discussed in #1769 · 1 comment · Fixed by #1821
Closed

Scaling of interfacial currents with particle shape #1781

valentinsulzer opened this issue Nov 3, 2021 Discussed in #1769 · 1 comment · Fixed by #1821
Assignees

Comments

@valentinsulzer
Copy link
Member

Discussed in #1769

Originally posted by dion-w October 31, 2021
hello everyone,
i have a question concerning the submodel "particle shape" : "user". I know that with this parameter you can reduce the amount of surface of your active material. For example if the particle shape is non-spherical or if some parts are blocked by the conductive binder fraction.

What i wonder: I tried some simulations with the user-supplied particle shape. Normally when you supply a very low current to your cell you get almost the theorethical capacity out of your cell, but this is not the case here. For a setup with an electrode capacity of 6mAh/cm² (positive electrode thickness ~100 µm) i almost loose 2 mAh/cm² at C/10 when using a user-supplied particle shape instead of the standard 3 e_s / R.

I think this is due to incorrectly scaling the molar flux in the microscale. Normally (and for this i refer to the supporting_information.pdf of this paper) when you use a user-supplied surface area you only set the surface area of the macroscale to this specific value. To ensure charge conservation the molar flux in the boundary needs to be scaled withe the factor of user-supplied-particle shape divided by 3*eps_s/R (see equation S22 in the attached supporting information).

Nonetheless i don't know how to fix this in the code. I only have an idea so far which i will show for the positive electrode (same for negative electrode):

  • pybamm/parameters/lithium_ion_parameters.py: In method _set_scales() starting at Line 532, introduce not only a_p_typ and but also a blockage quotient (maybe called "a_block") being calculated with .

  • pybamm/models/submodels/interface/kinetics/butler_volmer.py: could be used here in line 35 as an additional prefactor. Maybe it can used the same in other _get_kinetics methods of the interface subomdell, i don't know.

There may be a better name than since if is 1, no current is blocked but i didn't come up with a better name so far.

So what do you think about it?

@valentinsulzer valentinsulzer self-assigned this Nov 10, 2021
@valentinsulzer
Copy link
Member Author

I'm going to remove the "particle shape": "user" option (particle shape should always be consistent with the geometry) and add an "interface utilization" factor, which goes directly into the kinetics (i.e. total j is unchanged but overpotentials are affected)

valentinsulzer added a commit that referenced this issue Nov 17, 2021
valentinsulzer added a commit that referenced this issue Nov 17, 2021
valentinsulzer added a commit that referenced this issue Nov 17, 2021
valentinsulzer added a commit that referenced this issue Nov 17, 2021
valentinsulzer added a commit that referenced this issue Nov 17, 2021
valentinsulzer added a commit that referenced this issue Nov 18, 2021
valentinsulzer added a commit that referenced this issue Nov 19, 2021
valentinsulzer added a commit that referenced this issue Nov 19, 2021
valentinsulzer added a commit that referenced this issue Nov 22, 2021
valentinsulzer added a commit that referenced this issue Nov 24, 2021
valentinsulzer added a commit that referenced this issue Nov 24, 2021
valentinsulzer added a commit that referenced this issue Nov 25, 2021
valentinsulzer added a commit that referenced this issue Nov 27, 2021
valentinsulzer added a commit that referenced this issue Nov 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant