Fix reading of lammpsdump ATOM card. #3360
Conversation
… fix-lammpsdump-parser
|
Hello @hmacdope! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:
Comment last updated at 2021-08-21 05:17:47 UTC |
Codecov Report
@@ Coverage Diff @@
## develop #3360 +/- ##
========================================
Coverage 93.70% 93.70%
========================================
Files 177 177
Lines 22990 23017 +27
Branches 3247 3257 +10
========================================
+ Hits 21542 21569 +27
Misses 1397 1397
Partials 51 51
Continue to review full report at Codecov.
|
richardjgowers
left a comment
There was a problem hiding this comment.
What happens when multiple coordinate columns are present?
IAlibay
left a comment
There was a problem hiding this comment.
Couple of quick comments, probably needs more tests?
Co-authored-by: Irfan Alibay <IAlibay@users.noreply.github.com>
Co-authored-by: Irfan Alibay <IAlibay@users.noreply.github.com>
|
I think I have addressed everyone's comments :) |
|
Do people have any further comments? :) |
IAlibay
left a comment
There was a problem hiding this comment.
I think we're nearly there, but I'm a little bit hesitant since I'm not sure how modular the standard is, can coordinates be in the wrong order? Or does it not matter - does the way we loop through coord_cols on setting positions enforce ordering?
@MDAnalysis/coredevs if you have a chance to look here, maybe we can sneak this into 2.0.
Co-authored-by: Lily Wang <31115101+lilyminium@users.noreply.github.com>
Co-authored-by: Lily Wang <31115101+lilyminium@users.noreply.github.com>
|
@richardjgowers do you want to review / approve since you still have a blocking review? |
Fixes #3358
Supersedes #2333
Changes made in this Pull Request:
distances.transform_StoRis no longer applied by default, only if the coordinates are in thescaled (xs,ys,zs)orscaled_unwrapped (xsu, ysu, zsu)conventionPR Checklist