-
Notifications
You must be signed in to change notification settings - Fork 1
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
Generalize ff interaction #360
Conversation
2 failed, 94 passed, ready for review |
Which are the failing tests? tox looks fine. I'd advise to run black before the review so that we have common formatting, otherwise we might get confused with line numbers during it. |
Integration as always. It's formatted with the latest black version now. To me the docs action failure looks like some parts of the action are outdated. |
To use the new features of this PR, the plugins (at least both HAT ones) would have to be updated as well |
ah, looks like the doc parser is now attempting to parse every heading in the docstring as a proper semantic section, but https://github.com/hits-mbm-dev/kimmdy/blob/ce1daf0e68627c04e16c878e0d4d8f897ad5c833/src/kimmdy/parsing.py#L108-L109 is just a random heading I threw in, so this just has to not be a section by removing the |
would you like me to do small fixes directly in the PR when I review or just comment instead? |
Just change it |
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 some minor questions I can then also fix myself if you approve.
For radicals, the workflow is different between writing Regarding residuetypes, it is similar. No section means we want to use the one in the force field. Having aminoacids.rtp as default would mean we need it in the rundir. Feel free to rename the functions for finding and setting the atoms attribute. If you find ways to make the same logic more elegant I would be happy. It felt quite awkward to do it like this. |
…nto feat/generalize_ff
Deal with problems discussed in #359 and facilitate future addition of non-amber force-fields to kimmdy.