OpenFreeEnergy / OpenFreeEnergy/openfe

Bugs on handling interactions groups during hybrid topology construction?

Open
#1,159 3 comments 1 reaction 0 assignees View on GitHub

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:

  1. 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 between unique_new_atoms and unique_new_atoms will be computed twice? So does unique_old_atoms. This point should be a bug?

  2. Why not add the interactions between environment and environment, which should be added by sterics_custom_force.addInteractionGroup(environment_atoms, environment_atoms)?

  3. This function only deals with the sterics interactions. Why not add these interaction groups for electrostatics interactions?

Looking forward to your comments. Thanks!

Pengfei

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.