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

example_scripts-Different C rates #27

Open
Santiagopeacely opened this issue Feb 29, 2024 · 3 comments
Open

example_scripts-Different C rates #27

Santiagopeacely opened this issue Feb 29, 2024 · 3 comments

Comments

@Santiagopeacely
Copy link

Santiagopeacely commented Feb 29, 2024

hello, I am sorry to bother you.
I am a student.I think your team is good for this work,but I need help recently. This problem has been bothering me for a few days.What I need to do?
When the case of different C rates in example_scripts is running, no parameters are changed. Why are the cut-off voltages obtained by three different ratios not about 2.5V, but between 3.1, which can't match the data of journal papers? Why?
image

@lionsimbatoolbox
Copy link
Owner

Hello. The simulation you are running assumes thermal dynamics enabled. Try to disable them and re run the simulation. That should drive the 2.5V simulation fine.

@Santiagopeacely
Copy link
Author

Hello, I'm sorry to bother you again.
I tried to turn off the thermodynamic model again, the result is still not like the paper, I also tried to adjust the other models to enable and close, still can't achieve the effect in the paper, the result trend is right, but the discharge cut-off voltage is never up to 2.5V, including other cases, and the data results in the paper can not be well matched, I hope you can help me answer. If you can, I'd love if you can provide me with the source code of the case in the paper, and I'd like to try to run it and see if it matches the data in the journal. This is used to deduce the problem.
1709258239026
example_scripts:CarCycling_example2
image
https://iopscience.iop.org/article/10.1149/2.0291607jes

@lionsimbatoolbox
Copy link
Owner

Since it's very initial release, the code has been undergoing refactoring and some of the parameters may have been updated, or new equations introduced. While the code should have kept the backward compatibility, it may be that some of the default values for some of the parameters, or type of model approximations of some equations, changed. My suggestion is to checkout an older version of the framework (either 2.0 or 1.024) and use that as reference.

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

No branches or pull requests

2 participants