OpenFreeEnergy / OpenFreeEnergy/openfe
Bugs on handling interactions groups during hybrid topology construction?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 332
- Forks
- 56
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 13
Description
Hi, there,
About the function _handle_interaction_groups() of the source code file openfe/protocols/openmm_rfe/_rfe_utils/relative.py, I have several questions:
-
According to the document on the function
addInteractionGroup(), it has the following feature:
If a particle pair appears in two different interaction groups, its interaction will be computed twice. This is sometimes useful, but be aware of it so you do not accidentally create unwanted duplicate interactions.
If so, the interactions betweenunique_new_atomsandunique_new_atomswill be computed twice? So doesunique_old_atoms. This point should be a bug? -
Why not add the interactions between
environmentandenvironment, which should be added bysterics_custom_force.addInteractionGroup(environment_atoms, environment_atoms)? -
This function only deals with the
stericsinteractions. Why not add these interaction groups forelectrostaticsinteractions?
Looking forward to your comments. Thanks!
Pengfei
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with _handle_interaction_groups() in openfe/protocols/openmm_rfe/_rfe_utils/relative.py and read the addInteractionGroup() documentation it references. Trace how unique_new_atoms, unique_old_atoms, and environment are passed to the sterics custom force, then compare the handling of sterics and electrostatics. Done means resolving the three interaction-group questions and documenting or filing a specific corrective change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100