-
Notifications
You must be signed in to change notification settings - Fork 51
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
dhdl plot for the TI #110
dhdl plot for the TI #110
Conversation
Co-authored-by: Oliver Beckstein <orbeckst@gmail.com>
Codecov Report
@@ Coverage Diff @@
## master #110 +/- ##
==========================================
+ Coverage 97.30% 97.56% +0.25%
==========================================
Files 14 15 +1
Lines 743 822 +79
Branches 150 167 +17
==========================================
+ Hits 723 802 +79
Misses 5 5
Partials 15 15
Continue to review full report at Codecov.
|
@orbeckst I'm sorry that I felt that I cannot bump the test coverage to any higher. However, there are two regions that I'm not quite sure of what it does.
This function exists to make sure that there won't be too many ticks in the x axis.
but cannot get it fully covered. The other part is
Which my understanding is to deal with the case when there are too tittle ticks in the x axis.
but cannot get it fully covered. |
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 and kudos for pushing up coverage as high as you did – it's hard with plots!
Given that you identified the code pieces that are hard to test, mark them explicitly as not included in coverage. Something like
# pragma: no cover
You might have to find out how exactly to do this (we do it in MDAnalysis) but with this you explicitly acknowledge that certain code is untested and then it's removed from the coverage calculation.
@orbeckst Thank you for the advice. I have commented out the relevant lines with |
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 for adjusting coverage. I just saw two things to change: raise exceptions instead of using assertions for input checking – this was probably already in alchemical-analysis but should certainly not be in alchemlyb.
EDIT: Please also add an entry to CHANGES.
Otherwise, this looks excellent.
Thank you @xiki-tempula !! 🚀 |
Partially addresses #73
I have ported the dhdl plot for TI from the alchemical analysis.
Based on user experience, I have changed a few things.