it would be good to know a bit more about your system to evaluate
which is the simplest way (how complex is your molecule on
coarse-grained level?). You will be able to parse your lammps
trajectories and use them as a topolgoy, but using lammps for the
iterative process would require some modifications of the scripts.
VOTCA supports reading of lammps trajectories, if you name them with
the ending .dump. These can also be used as topologies by specifying
an additional xml file. I tested it using the following in the lammps
script:
dump id all custom 100 system.dump x y z fx fy fz (forces are optional)
This can be used directly as trajectory, but for a topology and
additional file specifying the molecule information is necessary. If
you want to use that as a topology, you'lll have to specify an
additional xml file topol.xml where molecules and names are specified
(in the manual is a similar example using a pdb file).
<topology base="system.dump">
<molecules>
<clear/>
<define name="water" first="1" nbeads="3" nmols="1000"/>
</molecules>
</topology>
then you can use e.g:
csg_map --top topol.xml --trj system.dump --cg bla.xml ...
To summarize: the missing bit is this xml file, you can use .pdb,
.dump, .tpr as base files. Lammps can probably directly write molecule
information. I didn't had it in my example and am not so familiar with
lammps, so it's not implemented yet. Be aware that csg_gmxtopol will
require some manual adjustments of the topology file.
If you want to use IBI or IMC: the scripts to run lammps simulations
are not yet implemented since we didn't use it here. One way is to run
the iterative procedure using gromacs (which should not be hard to
setup and i can guide you to a proper example depending on your
coarsee-grained topology). Otherwise, if you want to use lammps for
coarse-grained iterations (it needs to support tabulated potentials
then), you'll have to modify a few scripts (~ 3 scripts and maybe 30
lines of code).
Let me know which way you would prefer and we can post further details
how to proceed.
Cheers,
Victor
2011/6/21 Sacha Mould <sach...@gmail.com>:
> --
> You received this message because you are subscribed to the Google Groups "votca" group.
> To post to this group, send email to vo...@googlegroups.com.
> To unsubscribe from this group, send email to votca+un...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/votca?hl=en.
>
>
I guess your question boils down to this:
> Until now everything seems to work fine, although when i check cg.gro
> file using VMD ijust get unconnected dots instead of chains with 10
> beads. Is it normal?
This is normal. VMD draws bonds according to a standard cutoff. So if you don't see them in your cg.gro, this just means that the distances between your CG beads is larger than that value.
If you still want to see the bonds, you can either:
(1) Create and load an additional file (PSF) which contains the connectivity
or
(2) Use the "dynamic bonds" representation as described below:
http://www.ks.uiuc.edu/Research/vmd/mailing_list/vmd-l/2797.html
Hope this helps,
- Mara
see the cg hexane
<http://code.google.com/p/votca/source/browse/hexane/ibi/topol.top?repo=tutorials>
or cg spc/e
<http://code.google.com/p/votca/source/browse/spce/ibi/topol.top?repo=tutorials>
topology as an example.
Before I execute csg_inverse, I normally do a sanity check by run
grompp in the IBI main directory.
It should give no error message. Then I execute mdrun, which should
fail with an error like
"table_CG_CG.xvg not found". The missing table will later be generated by VOTCA,
see the gromacs.table option inside interaction block of your xml setting file.
Remember that the common table "table.xvg" needs to be generated
somehow and added to the filelist by you.
Cheers,
Christoph
2011/7/4 Sacha Mould <sach...@gmail.com>:
> --
> You received this message because you are subscribed to the Google Groups "votca" group.
> To post to this group, send email to vo...@googlegroups.com.
> To unsubscribe from this group, send email to votca+un...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/votca?hl=en.
>
>
--
Dr. Christoph Junghans
Votca Core Developer
Web: http://www.votca.org