Skip to content
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

Hydrogen mapping #47

Open
pbuslaev opened this issue Jul 31, 2024 · 2 comments
Open

Hydrogen mapping #47

pbuslaev opened this issue Jul 31, 2024 · 2 comments

Comments

@pbuslaev
Copy link

In the develop python3-adapted branch, I am a bit puzzled with the logics behind this line
To give an example, if I try to modify *-C into *-CC, hydrogens of methyl group are never mapped to hydrogens of the first carbon of ethyl group. Thus, efficiently in the resulting hydrid topology carbon will be bonded to 5 hydroges (three real ones and two dummy ones). This actually blocks using the hmr with GROMACS. But it also looks a bit strange to me in general.

@vgapsys Could you maybe share the idea behind this line? I tested internally and with commenting out this condition I am getting reasonable mappings which I can use with hmr. The following code maps hydrogens to minimize rmsd, which makes sense to me and allows runs with hmr.

pbuslaev added a commit to pbuslaev/pmx that referenced this issue Aug 20, 2024
@pbuslaev
Copy link
Author

@vgapsys I tested this change on our internal compounds and I don't see any reason why not to do this modification.

@vgapsys
Copy link
Member

vgapsys commented Aug 22, 2024

My concern is that such mappings might introduce internal strain due to the bonded interactions via dummy atoms. The cleanest way to avoid this is by avoiding the mapping itself.

Regarding hmr, if we are to use two topologies with hmr and map them with the current mapping scheme, all should work properly. I wonder why internal gmx hmr implementation cannot do this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants