-
-
Notifications
You must be signed in to change notification settings - Fork 597
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
Implement discharge capacity
as an optional x-axis in QuickPlot
#4775
base: develop
Are you sure you want to change the base?
Conversation
I have implemented the necessary changes for handling 0D variables. Once this is confirmed to be working correctly, I plan to work on handling 1D and 2D variables. Additionally, I have made changes in the |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #4775 +/- ##
========================================
Coverage 98.71% 98.71%
========================================
Files 304 304
Lines 23495 23514 +19
========================================
+ Hits 23192 23211 +19
Misses 303 303 ☔ View full report in Codecov by Sentry. |
Hello @agriyakhetarpal could please give a review on this? :) |
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.
Thanks, this is a good start.
Variables should always be evaluated with time, not discharge capacity.
Also, the implementation would be simpler if you just set self.x_axis
, self.x_min
and self.x_max
once and used those everywhere, instead of having the if/else for time and discharge capacity in so many places
b0498dc
to
5e0b742
Compare
I have made the suggested changes, I would like a review on if the plot functionality is working correctly or do I have to make some other changes. |
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.
I think the change looks good, could you please add a test or two? I expect the coverage to go down as you have a few branches in the code now (i.e., one for time, and one for discharge capacity).
Do I also have to make similar changes for 1D and 2D variables? or are they simply not applicable in those cases? |
For now I have added tests for the function , let me know if any other changes are to be made
Also suggest how to move forward with this? |
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.
This is almost there, just a few more comments
I have made the suggested changes, if anyone could review this one :) |
It looks good to me, just three missing lines in the coverage. Thanks for your work! |
I have added tests for the missing lines, are there any other improvements I need to make ? |
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.
Nice work, thanks, @medha-14! I am happy to approve this, though I'll also request @valentinsulzer for a review as he previously requested changes.
Description
Fixes #1751
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 -m pytest
(or$ nox -s tests
)$ python -m pytest --doctest-plus src
(or$ nox -s doctests
)You can run integration tests, unit tests, and doctests together at once, using
$ nox -s quick
.Further checks: