[gmx-users] Problem in equilibration for membrane system

Bing Bing jarbing09 at gmail.com
Wed Oct 7 10:39:05 CEST 2009

My protein complex was minimized initially before putting into the lipid.
POPC is also a preequilibrated structure from Tielemen website. I don't
quite understand on what you meant by "the protein is not happy with the
restraint". The system went well through out the nvt, npt with restraint on
protein.... Once it move to md production run ( which is without restraint
on protein), error occurred (range checking error).
The reason i'm using the version3.3.2 is because the forcefield i'm using at
the moment only support version3.3.2.  Is my problem cause by bug of the
older version? is there any bugfix fot this? please


On Wed, Oct 7, 2009 at 4:15 PM, Mark Abraham <Mark.Abraham at anu.edu.au>wrote:

> Bing Bing wrote:
>> Dear All,
>> I'm running the protein complex with POPC system. NVT (100ps) and NPT
>> (200ps) were done with restraint on the protein follow by 1000 ps of NPT
>> without restraint on protein. The trajectory was checked in term of
>> pressure, potential, area per lipid ....were checked and everything seems ok
>> (potential almost plateu, area per lipid close to experimental value). I
>> proceeded with md (similar to Justin's tutorial) for 1 ns. The simulation
>> stop around 800ps with the range checking error.
> OK so look at the collective variables, and/or trajectory to find evidence
> of the problem. The most likely explanation is that your protein was unhappy
> in the restraints, of course. Perhaps you should try some vacuum EM before
> you embed it in the lipid, or some such.
>  I'm using gromacs 3.3.2, with GROMOS9653a6 forcefield. I tired to be more
>> gentle while releasing the restraint.Different stepwise of releasing the
>> restraint during NPT were tried and followed by production MD, all the
>> simulation stop or i shall said it crashed around ~800ps with the same error
>> (range checking error). I'm out of idea what is the problem here. Please
>> advice.
> Range checking is just one of many things that can be the first thing to
> break when there's an underlying systemic problem.
> Also, unless you need scientific continuity, 3.3.2 is about 4 years old...
> 4.0.5 will be much faster!
> Mark
> _______________________________________________
> gmx-users mailing list    gmx-users at gromacs.org
> http://lists.gromacs.org/mailman/listinfo/gmx-users
> Please search the archive at http://www.gromacs.org/search before posting!
> Please don't post (un)subscribe requests to the list. Use the www interface
> or send it to gmx-users-request at gromacs.org.
> Can't post? Read http://www.gromacs.org/mailing_lists/users.php
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://maillist.sys.kth.se/pipermail/gromacs.org_gmx-users/attachments/20091007/79c69312/attachment.html>

More information about the gromacs.org_gmx-users mailing list