Adding elements attribute to PDB parser and unit tests#2648
Adding elements attribute to PDB parser and unit tests#2648AmeyaHarmalkar wants to merge 1 commit intoMDAnalysis:developfrom
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #2648 +/- ##
===========================================
+ Coverage 90.61% 91.01% +0.39%
===========================================
Files 174 174
Lines 23554 23607 +53
Branches 3072 3086 +14
===========================================
+ Hits 21343 21485 +142
+ Misses 1585 1498 -87
+ Partials 626 624 -2
Continue to review full report at Codecov.
|
|
@IAlibay the new PR for the issue like you suggested. |
|
@AmeyaHarmalkar I think there has been some misunderstanding, I meant that you should finish PR #2627 solely allowing for elements to be parsed if they are all present & normal (as you are doing here). Then open up a new PR/issue set for dealing with alternative cases where elements are non-normal, including any appropriate changes to |
|
Oh, I completely misunderstood you then. Should I do a hard reset on the other branch then do the changes? I will close this PR and delete the issue. |
Sorry about that, this is definitely on me for bad communications. Probably closing this PR would be a good idea, however you can keep the issue open, just add it to the header of #2627 and we can close it when we merge the PR. Re: hard reset -> just revert the one file, you can do that using git checkout: https://stackoverflow.com/questions/215718/how-can-i-reset-or-revert-a-file-to-a-specific-revision |
Fixes #2647
Changes made in this Pull Request:
PR Checklist