-
Notifications
You must be signed in to change notification settings - Fork 652
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
Hbond analysis update #4107
Hbond analysis update #4107
Conversation
…arison of arrays to use numpy.testing.assert_allclose function
Linter Bot Results:Hi @yickysan! Thanks for making this PR. We linted your code and found the following: Some issues were found with the formatting of your code.
Please have a look at the Please note: The |
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## develop #4107 +/- ##
===========================================
- Coverage 93.59% 93.56% -0.03%
===========================================
Files 192 192
Lines 25133 25144 +11
Branches 4056 4060 +4
===========================================
+ Hits 23523 23526 +3
- Misses 1092 1097 +5
- Partials 518 521 +3
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
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.
Hi @yickysan, thanks for you contribution. It looks like in this PR you also have the changes that you did for PR #4090. Could you please remove/revert them?
I see you are correctly working on a specific branch for this fix (yickysan:hbond-analysis-update
) which is great. You probably created this branch from yickysan:numpy.testing-function-change
, instead of creating it from develop
and that's likely why you have both changes in this branch.
Hello, |
@yickysan as you can see from the files changed, deleting the You will need to revert the changes in this branch. You can probably use (These are the commits that you also had in the other PR (see MDAnalysis/pull/4090/commits and the commit message appears to be related to the tests). |
I am currently reverting these commits as well. |
670b9f9
to
8f8a48e
Compare
8f8a48e
to
d455e4e
Compare
Please I need your help. In an attempt to revert the commits I have accidentally deleted some files. Anyway you can help me through this?
Hello is it possible to close this pull requests while I make another one? I think in my attempt to revert the other commits I might have broken something.
|
How did you delete the file? Were you using Don't be discouraged by these difficulties with |
I think I must have accidentally deleted the file trying to handle a merge conflict. I used git reset and not revert. I have redownloaded the file and added it back to my local repo. |
Make sure to commit and push, so that the file is restored in this PR as well. If everything goes well, it should disappear from the "files changed" tab. You can read here about the difference between reset and revert: https://git-scm.com/docs/git#_reset_restore_and_revert The latter is safer because it does not change the commit history. |
89999dd
to
7c98e9f
Compare
@yickysan Looks like you removed all the changes, including the ones related to this PR? There is nothing to review at the moment. (I'm on mobile, apologies if I missed something ing.) |
You can use "git status" and "git diff" locally to check what's going and in which state is your (local) repo. |
Yes the revert I made removed the file related to this pull request but I am adding it back right now. |
Hello @RMeli I added back the commit related to this PR. It failed the codecov tests. Is there a way to fix 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.
I'm not sure I understand the intent behind these changes, how is this intended to change the usability of the hbond analysis class? Maybe if you can provide a quick walked through example of how a user might help review.
re coverage: this is happening because you don't have any tests that cover the new code branches that were introduced in this PR. To avoid them, you would need to add tests that try out the new input method you've introduced.
] | ||
if select: | ||
|
||
ag = self.u.select_atoms(select) |
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.
Ratther than doing a completely new code branch for each option, why not just do this selection solely in an if/else and leaving everything else the same?
So it doesn't change the usability of the hbondanalysis class. It just changes the |
Fixes #3933
Changes made in this Pull Request:
ag.atoms
instead ofag.select.atoms("all")
if a selection string isn't given.PR Checklist
📚 Documentation preview 📚: https://readthedocs-preview--4107.org.readthedocs.build/en/4107/