-
Notifications
You must be signed in to change notification settings - Fork 663
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
Lammps Dump Parser #3844
Lammps Dump Parser #3844
Conversation
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 for the contribution @jaclark5! It's looking great so far. See my comments. We will also need some tests with a small imageflag
containing testfile. :)
It may also be better to split the imageflag
and forces+velocities stuff into separate PRs to avoid this one becoming super crowded but up to you at the end of the day.
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.
Some more quick comments from a read over.
Co-authored-by: Hugo MacDermott-Opeskin <[email protected]>
Codecov ReportBase: 94.35% // Head: 94.35% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## develop #3844 +/- ##
========================================
Coverage 94.35% 94.35%
========================================
Files 194 194
Lines 25031 25062 +31
Branches 3374 3390 +16
========================================
+ Hits 23617 23648 +31
Misses 1365 1365
Partials 49 49
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 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.
Few comments :)
coords = coords[:3] | ||
coords += images * ts.dimensions[:3] | ||
else: | ||
raise ValueError("Cannot unwrap coordinates without image flags.") |
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.
You will need to add a test that covers 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.
Looking good, just a few suggestions.
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.
Almost there, quick comment and will await some feedback from @PicoCentauri
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 happy with this now. :) Anyone else want to review or shall we go ahead.
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.
Couple things on my end, mostly pep8
@@ -455,7 +455,7 @@ class DumpReader(base.ReaderBase): | |||
"""Reads the default `LAMMPS dump format`_ | |||
|
|||
Supports coordinates in the LAMMPS "unscaled" (x,y,z), "scaled" (xs,ys,zs), |
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.
We really need a Parameters
section for this parser, this is too much text for folks to read and understand what's going on.
I'm happy having this be addressed in a follow-up PR, but can an issue be raised please?
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 thanks!
Hmm I thought this was supposed to merge upon approval, do I need to do anything else? |
I was just waiting on CI, I'll merge now (we don't have merge on approval set up, it's something the coredevs need to discuss at some point I guess) |
Fixes #3843 #3741
Changes made in this Pull Request:
PR Checklist