-
Notifications
You must be signed in to change notification settings - Fork 0
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
Move things to utils, test interchange creation #47
Conversation
Hello @hannahbaumann! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:
Comment last updated at 2024-09-26 12:24:25 UTC |
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
smc_components = {} | ||
prot_settings = GromacsMDProtocol.default_settings() | ||
# The function expects a settings dict | ||
settings = {} |
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.
create_openmm_systems
takes in a settings dict, which in the protocol is created using the _handle_settings
function. This makes this test not so pretty, as I have to create the dictionary. Should I change the function to instead take in the actual settings objects? Or is this ok?
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.
Yes, I would encourage changing the method to not take in the whole dictionary unless you can avoid it. If you only rely on a couple of settings, it can make life a lot easier (if it's a whole bunch of settings then that's a different issue).
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 changed this to instead pass in the individual settings. Alternatively, I was thinking we could also have an SystemCreationSettings
class that contains the settings necessary to create the OpenMM system to distinguish with the settings that are related to Gromacs. But I'm not sure if that would be confusing to the user.
for more information, see https://pre-commit.ci
smc_components = {} | ||
prot_settings = GromacsMDProtocol.default_settings() | ||
# The function expects a settings dict | ||
settings = {} |
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.
Yes, I would encourage changing the method to not take in the whole dictionary unless you can avoid it. If you only rely on a couple of settings, it can make life a lot easier (if it's a whole bunch of settings then that's a different issue).
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
…gromacs into move_things2utils
for more information, see https://pre-commit.ci
…gromacs into move_things2utils
for more information, see https://pre-commit.ci
…gromacs into move_things2utils
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! just a couple of issues worth raising for future work.
Description
This PR seeks to address the following issues:
create_interchange
and_assign_partial_charges
to their own utilities #30mdout.mdp
is being written outside ofshared
andscratch
directories. #53