Notebook example files added for ECM and folder structure updated.#460
Conversation
…files added for single pulse and multi-pulse HPPC data fitting, a thermal submodel is also added. Folder created to keep data files for running example cases.
…7-add-thermal-thevenin-example-remove-params-from-others
88f9832 to
75d66b8
Compare
…ers' of https://github.com/pybop-team/PyBOP into 437-add-thermal-thevenin-example-remove-params-from-others
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #460 +/- ##
========================================
Coverage 99.04% 99.04%
========================================
Files 52 52
Lines 3559 3559
========================================
Hits 3525 3525
Misses 34 34 ☔ View full report in Codecov by Sentry. |
…for performance, small fixes/formating to notebooks
…le-remove-params-from-others # Conflicts: # examples/notebooks/equivalent_circuit_identification.ipynb
…arams-from-others
|
I thought we had a stale PR diff for |
|
Yes, I haven't changed this file. So you mean this file needs to be pushed as a commit? |
|
Yes, one way is to restore the notebook to develop state and move it again before committing. The below command should restore the file to develop state. git restore -s develop examples/notebooks/LG_M50_ECM/1-single-pulse-circuit-model.ipynb |
|
Great, thanks! |
|
Do you still want the |
|
Agreed, let's keep it under the notebook subdirectory |
|
I think now we are good to go. |
BradyPlanden
left a comment
There was a problem hiding this comment.
Thanks for these additions @Dibyendu-IITKGP - they look great! I'll merge once the tests finish.
|
@all-contributors please add @Dibyendu-IITKGP for examples |
|
I've put up a pull request to add @Dibyendu-IITKGP! 🎉 |
Description
Notebook example files are added for single pulse and multi-pulse HPPC data fitting, a thermal submodel is also added. Folder structure updated to keep data files for running example notebook files.
Issue reference
Fixes #437
Review
Before you mark your PR as ready for review, please ensure that you've considered the following:
Type of change
Key checklist:
$ pre-commit run(or$ nox -s pre-commit) (see CONTRIBUTING.md for how to set this up to run automatically when committing locally, in just two lines of code)$ nox -s tests$ nox -s doctestYou can run integration tests, unit tests, and doctests together at once, using
$ nox -s quick.Further checks:
Thank you for contributing to our project! Your efforts help us to deliver great software.