-
Notifications
You must be signed in to change notification settings - Fork 674
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
bug fix double counting water in Water bridge analysis #3120
Conversation
Hello @xiki-tempula! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found: There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻 Comment last updated at 2021-05-07 06:59:13 UTC |
Codecov Report
@@ Coverage Diff @@
## develop #3120 +/- ##
========================================
Coverage 93.03% 93.03%
========================================
Files 172 172
Lines 22724 22725 +1
Branches 3193 3194 +1
========================================
+ Hits 21141 21142 +1
Misses 1533 1533
Partials 50 50
Continue to review full report at Codecov.
|
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.
Mechanically, a new unit test has been added, the tests are passing, and the patch diff is 100 %.
I'm perhaps a little confused here because I'm not familiar with this analysis module, so I've asked a question about the desired order here.
Acceptor···H−O···H-Donor | ||
| | ||
H···O-H | ||
will be recognised as 3rd order water bridge. |
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.
The matching issue has "Will be recognised as a third-order water bridge" under the "expected behavior" section?
Is this supposed to be a "first order" water bridge because only one water actually contacts both the acceptor and donor? Or is it second order because of propagation into the "extra water" on the side?
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.
@tylerjereddy I'm sorry. I didn't realise that it is in the expected behaviour section. I have amended the issue to reflect that.
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.
lgtm - though (possible naive question), is there a reason for not doing the check for duplicates until the end rather than as you're building the routes? I would have thought the latter would be faster, but I may be wrong.
@fiona-naughton Thanks for the review. |
@xiki-tempula are you going to fix #3259 as part of this PR? |
@fiona-naughton , what needs to be done to merge by Friday? |
I have resolved the conflicts in case this could be merged today. |
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 @xiki-tempula - I'll let the checks finish running, but lgtm!
Fixes #3119
Changes made in this Pull Request:
Previously, Water bridge analysis counts the duplicated water via checking if the same hydrogen bond is being used.
For example,
Will give
A1···H2-O3
O3-H4···O5
O5-H6-A1
A1···H2-O3
O3···H7-D8.
This will get rejected as
A1···H2-O3
appear twice. However, it doesn't check if O3-H4···O5 and O5···H4-O3 can exit at the same time and this PR fixed it.PR Checklist