Open ctk3b opened 10 years ago
Fantastic detail. This helps us really understand what is going on and the range of time it will take. Most of these will be easy, if somewhat time intensive. Others will be harder . . .
I'm trying to figure out the best way to write out DihedralTrig
in LAMMPS.
LAMMPS appears to support RB style dihedrals but only out to 5 coefficients: http://lammps.sandia.gov/doc/dihedral_multi_harmonic.html
Alternatively we have the CHARMM convention which should function just like proper 1 (or 9 with multiple entries): http://lammps.sandia.gov/doc/dihedral_charmm.html
Does using multi-harmonic for anything with c6=0 and otherwise decomposing to CHARMM style sound like a reasonable approach?
At some point, we may also need to support a distinction between CHARMM and other forcefield so that LAMMPS ends up using the correct pairstyle (I need to do more reading here).
Check out the gromacs writing logic- i had to go through pretty much the same process for the conversion. Including c6=0.
Out of contact for 24 hours or so- boarding plane'
Sent from my iPhone
On Jun 6, 2014, at 16:55, Christoph Klein notifications@github.com wrote:
I'm trying to figure out the best way to write out DihedralTrig in LAMMPS.
LAMMPS appears to support RB style dihedrals but only out to 5 coefficients: http://lammps.sandia.gov/doc/dihedral_multi_harmonic.html
Alternatively we have the CHARMM convention which should function just like proper 1 (or 9 with multiple entries): http://lammps.sandia.gov/doc/dihedral_charmm.html
Does using multi-harmonic for anything with c6=0 and otherwise decomposing to CHARMM style sound like a reasonable approach?
At some point, we may also need to support a distinction between CHARMM and other forcefield so that LAMMPS ends up using the correct pairstyle (I need to do more reading here).
— Reply to this email directly or view it on GitHub.
Note that LAMMPS also supports higher order terms for RB style dihedrals, via dihedral/nharmonic (http://lammps.sandia.gov/doc/dihedral_nharmonic.html), which is part of the USER_MISC package.
Where in your table would the input keywords:
bond_coeff
angle_coeff
dihedral_coeff
pair_coeff
be placed?
I'd say * Handling of all input commands
is an appropriate home
I'm just going to keep track of what needs to be done in LAMMPS here so if anyone who feels the desire to chip in on something knows where to look.