-
Notifications
You must be signed in to change notification settings - Fork 667
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
TPR reader sets chainID
from molblock
#4281
Conversation
Linter Bot Results:Hi @pgbarletta! 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 |
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 am in favor of your change, @pgbarletta.
Do the tests check that specific chainIDs were parsed?
Please also do the usual (update CHANGELOG, docs, ...). Ping me when you need me to review again.
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## develop #4281 +/- ##
==========================================
Coverage 93.40% 93.40%
==========================================
Files 170 184 +14
Lines 22250 23363 +1113
Branches 4071 4071
==========================================
+ Hits 20783 21823 +1040
- Misses 951 1024 +73
Partials 516 516
☔ View full report in Codecov by Sentry. |
I added the expected chainIDs to |
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. I think the testing is doing the right thing. It's a bit complicated and it took me a while to see what's happening with all the inheritance. The fact that you're testing a case with two chains gives me some confidence that it works.
Sorry for the delay, I had thought I had already done this review but obviously not... in general, feel free to ping me when a week has passed!
- issue number for PR - cleanup of other CHANGELOG entries
Thanks @pgbarletta ! |
I read through everything an decided at the very last minute that it was better to document what we are doing and added it. |
We do need to update the User Guide so I raised MDAnalysis/UserGuide#312 — could you please do that, @pgbarletta ? Thanks. |
Fixes #3994
Trying to revive this issue, following @orbeckst's suggestion (don't set
molblock
toSegments
, but tochainIDs
). As usual, I'll delete the PR and the issue if this is not deemed useful.Changes made in this Pull Request:
tpr_utils.do_mtop()
sets thechainID
of each atom as this:chainID = molblock[14:] if molblock[:14] == "Protein_chain_" else molblock
TPRAttrs
addschainIDs
to the listexpected_attrs
. I didn't thought it was necessary to add more tests on top of that.If approved I'll add 'chainID' here.
This does not warrant an addition to the
versionchanged
heading, right?PR Checklist
Developers certificate of origin
📚 Documentation preview 📚: https://mdanalysis--4281.org.readthedocs.build/en/4281/