Debian Codegraph @

examples/all_atom/force_field_OPLSAA/ethylene+benzene_PACKMOL/README_setup.sh

raw
1
2 # Create the coordinates of the atoms using PACKMOL
3 cd packmol_files
4
5 packmol < mix_ethylene+benzene.inp
6 mv -f system.xyz ../moltemplate_files/
7
8 cd ..
9
10
11
12 # Create LAMMPS input files this way:
13 cd moltemplate_files
14
15 # run moltemplate
16
17 moltemplate.sh system.lt
18
19 # --- OPTIONAL: ---
20 # You can also check for missing angle,dihedral params this way:
21 # moltemplate.sh -checkff system.lt
22 #
23 # You can also check for alternative possible OPLSAA parameters this way:
24 # moltemplate.sh system.lt -report-duplicates bytype __
25 # This will check to make sure that there was no ambiguity in the OPLSAA
26 # force-field parameters. Unfortunately, if you do that, moltemplate
27 # will create a "warning_duplicate_dihedrals.txt" which often contains
28 # more spurious warnings than you could possibly hope to read. Most
29 # OPLSAA molecule builder programs do not warn you about these ambiguities.
30 # Moltemplate does warn you, but in my experience, it's often not worth the
31 # trouble to worry about them. Just use: "moltemplate.sh system.lt"
32 # --- OPTIONAL: ---
33
34
35 # Moltemplate generates various files with names ending in *.in* and *.data.
36 # Move them to the directory where you plan to run LAMMPS (in this case "../")
37 mv -f system.data system.in* ../
38
39 # Optional:
40 # The "./output_ttree/" directory is full of temporary files generated by
41 # moltemplate. They can be useful for debugging, but are usually thrown away.
42 rm -rf output_ttree/
43
44 # Optional:
45 rm -f run.in.EXAMPLE # not needed. We have several run.in... files already.
46
47 # Optional:
48 # If any warnings were generated, move them to the parent folder
49 # (so they get noticed).
50 mv -f warning*.txt ../ 2> /dev/null
51
52 cd ../
53
54
55
56
57 # Optional:
58 # Note: The system.data and system.in.settings files contain extra information
59 # for atoms defined in OPLSAA which you are not using in this simulation.
60 # This is harmless, but if you to delete this information from your
61 # system.in.settings and system.in.data files, run this script:
62 #
63 # cleanup_moltemplate.sh