-
-
Notifications
You must be signed in to change notification settings - Fork 576
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
Change "Cell capacity [Ah]" to "Nominal cell capacity [Ah]" #1339
Comments
Hi there I am new here, does this issue only needs renaming? |
Hi @Saransh-cpp! Yes. You should also add a deprecation warning, but we can help you with that if you don't know where to place it. |
Yes thanks! That would be great. I have been exploring the codebase and looking for the "Cell capacity [Ah]" parameter but had no luck finding it. Can you please guide me by providing a file or a directory path where this is used? |
Sorry about that, there is a typo. You have to look for |
@brosaplanella thanks for the correction. I found a lot of references in the .csv of different cell under the input directory, in the test directory and also in files like simulation.py, electrical_parameters.py, parameter_values.py, test_lead_acid_parameters.py etc. Should I rename all the references to |
That's correct. Running the tests locally will help you spot if you missed any. |
Okay! Sorry I got a bit busy, I'll start working on it and try the deprecated warning also, if I have any problems I'll post them here:). |
@brosaplanella I should not rename Cell capacity in the CHANGELOG.md file right? Should I add a new line there saying |
Exactly, you shouldn't rename it in For the deprecating warning, it is a bit more tricky. We want to throw a warning saying that it will be deprecated in the next release but make the code still work with the current notation. You can find an example of a deprecation warning in line164 of |
The changelog does also list breaking changes and deprecations (though I don't know whether anyone actually looks at those) |
Sorry, my bad, I was thinking of the actual deprecation warning. An example on CHANGELOG is on line 78
|
Okay! I'll get on it. Thanks |
I've been trying but I don't completely understand where I should add the deprecated warning? Should I create another if condition after line 343 or 354 in parameter_values.py because I think that is the function where the values are being checked? |
Yes, that's it. What you can do is add a new block like the one on For the deprecation warning see the example in |
Hopefully this will make it clear that this parameter is only for converting C-rate to current.
The text was updated successfully, but these errors were encountered: