Will the LAMMPS input need to use user developed packages?
In addition, should we need to know how to execute interactive MD?
Another, should we need to know how to compile LAMMPS as a library and then coupling with other MD code?
Thanks,
Linda
Hi Stephanie,
you can use dump image to generate snapshots in the .ppm or .jpg formats. The image files can be concatenated into a movie, for example, using ffmpeg.
You can also use dump dcd to store a series of snapshots into a DCD file, which can be read in by VMD: http://www.ks.uiuc.edu/Research/vmd/
For example, in the LAMMPS input script you specify
# Write atom positions into xyz files every 100000 steps
dump 1 all xyz 100000 x_t*.xyz
# Write atom positions into a dcd file every 100 steps
dump 2 all dcd 100 trajectory.dcd
to generate x_t0.xyz, x_t100000.xyz, etc. and trajectory.dcd.
Then with VMD installed on your machine, you can visualize them by:
/path_to_vmd_bin/vmd x_t0.xyz trajectory.dcd
The MovieMaker plugin in VMD can be used to generate movies from the DCD file: http://www.ks.uiuc.edu/Research/vmd/plugins/vmdmovie/
Hope it helps,
-Trung
--
You received this message because you are subscribed to the Google Groups "SCC12" group.
To post to this group, send email to sc...@googlegroups.com.
To unsubscribe from this group, send email to scc12+un...@googlegroups.com.
Hi Linda and all,
Mike and I discussed and decided the following packages that will be sufficient for the test cases:
1- MANYBODY
2- MOLECULE
3- KSPACE
4- ASPHERE
5- RIGID
Regarding the input script for the test cases, you are allowed to make the following changes:
1- Toggle the newton flag on or off
2- Tune the atom sorting frequency (via atom_modify sort)
3- Use the optimized version of the pair styles and fixes available in OPT, GPU, USER-OMP and USER-CUDA (see the doc page of the pair styles and fixes).
4- Change the cutoff value of the Coulombic interaction (for example, in pair styles that consisting of a /coul/long term) when the kspace solver is used.
5- Change the neighbor list build settings (via the commands neighbor and neigh_modify) as long as the number of dangerous builds reported at the end of the runs is zero; otherwise (i.e. nonzero dangerous builds), the results will be considered incorrect.
6- Use run_style verlet/split to divide the work between real space calculations and k-space solver among CPUs.
7- Use the command balance for static load balancing, or fix balance for dynamic load balancing.
Let me know if you have further questions.
Best,
-Trung
To unsubscribe from this group, send email to scc12+un...@googlegroups.com<mailto:scc12+unsub...@googlegroups.com>.
To unsubscribe from this group, send email to scc12+un...@googlegroups.com<javascript:><mailto:scc12+unsub...@googlegroups.com<javascript:>>.