-
Notifications
You must be signed in to change notification settings - Fork 31
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
Fix mass and charge in GSD writer; Add angles and dihedrals to GSD writer #680
Conversation
This also contains another fix where the gsd writer was trying to call on |
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
This pull request introduces 1 alert when merging a537c3e into 2970412 - view on LGTM.com new alerts:
|
…one mass and charges in gsd writer
So, it looks like f-string formatting doesn't work when using it with |
hmm, that should not be the case, I used f-string with |
This pull request introduces 3 alerts when merging 918425b into c336588 - view on LGTM.com new alerts:
|
I'm not getting an error, but when running in a notebook, the variable name with brackets is in the warning statement rather than it actually performing the string formatting and printing the variable's value. I think I am missing a couple |
Codecov Report
@@ Coverage Diff @@
## develop #680 +/- ##
===========================================
+ Coverage 91.22% 91.47% +0.24%
===========================================
Files 63 63
Lines 5172 5217 +45
===========================================
+ Hits 4718 4772 +54
+ Misses 454 445 -9
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
This pull request introduces 3 alerts when merging 0d3f4f1 into c336588 - view on LGTM.com new alerts:
|
This pull request introduces 3 alerts when merging 9d1d195 into c336588 - view on LGTM.com new alerts:
|
Before we merge this, let me test it out with some more compounds from mBuild and make sure the information the gsd file is correct and makes sense. |
This pull request introduces 3 alerts when merging 4d0d34a into c336588 - view on LGTM.com new alerts:
|
This pull request introduces 3 alerts when merging 2fbc265 into c336588 - view on LGTM.com new alerts:
|
This pull request introduces 3 alerts when merging 36f30a4 into c336588 - view on LGTM.com new alerts:
|
The workflow in the latest unit test I added also solves mosdef-hub/mbuild#1025 |
This pull request introduces 3 alerts when merging 3ac2565 into cc23eb8 - view on LGTM.com new alerts:
|
This pull request introduces 3 alerts when merging 2ec890a into 0a11627 - view on LGTM.com new alerts:
|
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.
Slight update to docstring, the rest LGTM!
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! Would like some testing for more ways to write out GSD files and testing them, but until we have a more extensive set of things we want to be sure to support, I think we're good.
This pull request introduces 3 alerts when merging 847e4b0 into 0a11627 - view on LGTM.com new alerts:
|
This helps address #678 where the gsd writer was trying to perform math operations with
NoneType
objects.Still need to add a unit test
Edit: Some other errors popped up, and I ended up totally revamping the gsd writer. It is writing out angles and dihedrals now.
Edit: I edited the title again to better reflect the changes by the PR. After talking with Cal in #678 there aren't any changes to default mass and charge values.