-
-
Notifications
You must be signed in to change notification settings - Fork 554
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
Issue 4224 duration bug #4239
Issue 4224 duration bug #4239
Conversation
@valentinsulzer You need to take Alternatively you might think about |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, let's just add a line to CHANGELOG before merging.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #4239 +/- ##
===========================================
+ Coverage 99.54% 99.55% +0.01%
===========================================
Files 288 288
Lines 21886 21897 +11
===========================================
+ Hits 21786 21800 +14
+ Misses 100 97 -3 ☔ View full report in Codecov by Sentry. |
@brosaplanella @valentinsulzer To confirm, this is working as expected for the use cases on which I was testing. |
Changing default duration to 1000 hours caused a severe performance degradation, investigating further |
Thanks! I just tried it and though I'd prefer a longer duration barring a substantial performance hit, in my opinion, the bug is fixed by the warning alone. I wonder if 100 + ε hours might be a happy medium? |
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
This PR adds the warning and also fixes the C/100 case which I assume is more common than specifying a small current (backed up by a n=2 sample size from @aabills and @ejfdickinson ). The default duration is 24h and we can reconsider once @MarcBerliner is done with updates to solvers, which will make solve times much less sensitive to things like duration, period, etc |
* make longer default duration and calculate it for C-rate * add tests * typo * pybamm-team#4224 add warning for time termination and add abs * fix tests * pybamm-team#4224 keep non-C-rate default at 24h for performance reasons * trying to fix experiment * fix example * pybamm-team#4224 eric comments * fix bug
Description
Fixes #4224
longer default duration (1000 hours)Currently working on adding a warning if maximum duration is reached
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:
$ 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)$ python run-tests.py --all
(or$ nox -s tests
)$ python run-tests.py --doctest
(or$ nox -s doctests
)You can run integration tests, unit tests, and doctests together at once, using
$ python run-tests.py --quick
(or$ nox -s quick
).Further checks: