WHOLEMOLECULES not recognizing atoms, throws "no atom found for WHOLEMOLECULES!" error.

210 views
Skip to first unread message

manuv...@gmail.com

unread,
Sep 15, 2015, 10:54:43 AM9/15/15
to PLUMED users
Hi,

I am trying to use PLUMED for a metadynamics run of a membrane protein involving a function of COM as the CV. In order to ensure that the drift of my protein outside the PBC does not affect my value of COM I am giving the WHOLEMOLECULES directive to PLUMED. (WHOLEMOLECULES ENTITY=1-1246). However, when I pass this directive plumed shows an error - "no atom found for WHOLEMOLECULES!". Surprisingly it throws no error when I try to calculate the COM of these atoms which means that it is recognizing these atoms. I checked the source for WHOLEMOLECULES and the exception is thrown if the number of atoms in the group is 0, which is not the case here.

I am also calculating some angles later so I really need to get WHOLEMOLECULES working. Please suggest a solution for this issue. I don't know if it matters with this problem but I am using MARTINI with gromacs to simulate this system.


Versions tried: PLUMED - 2.13, 2.2b. GROMACS - 5.0.6

Regards,
Manu Vajpai
PhD Candidate
Department of Biological Sciences and Bioengineering
IIT Kanpur

Gareth Tribello

unread,
Sep 15, 2015, 10:55:52 AM9/15/15
to plumed...@googlegroups.com
Hello

I think you need to use either ENTITY0 or ENTITY1 rather than ENTITY.

Gareth

--
You received this message because you are subscribed to the Google Groups "PLUMED users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to plumed-users...@googlegroups.com.
To post to this group, send email to plumed...@googlegroups.com.
Visit this group at http://groups.google.com/group/plumed-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/plumed-users/9bd6129d-175d-49d2-8b79-d0cc6427ad64%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

manuv...@gmail.com

unread,
Sep 15, 2015, 11:21:38 AM9/15/15
to PLUMED users
Thank you! That fixed the issue.

Regards,
Manu Vajpai
Reply all
Reply to author
Forward
0 new messages