| 1 |
# Here we generate the starting coordinates of the simulation |
| 2 |
# using PACKMOL. |
| 3 |
|
| 4 |
|
| 5 |
|
| 6 |
# You must run each packmol commend one after the other. |
| 7 |
# |
| 8 |
# NOTE: If PACKMOL gets stuck in an endless loop, then edit the corresponding |
| 9 |
# "inp" file (edit the "tolerance" and "distscale"). This should not happen, |
| 10 |
# but keep in mind that PACKMOL can be very slow. (Step3 takes several days.) |
| 11 |
# |
| 12 |
# NOTE: You can also usually interrupt packmol after 1 hour. The solution |
| 13 |
# at that point (an .xyz file) should be good enough for use. |
| 14 |
# (Of course, you should check to see that the file exists and the |
| 15 |
# structure looks reasonable visually before interrupting packmol. |
| 16 |
# Small holes are okay. The simulation protocol we use should close them.) |
| 17 |
|
| 18 |
packmol < step1_proteins.inp # This step determines the protein's location |
| 19 |
# It takes ~40 minutes (on a 2015 intel i7) |
| 20 |
packmol < step2_innerlayer.inp # This step builds the inner monolayer |
| 21 |
# It takes ~10 hours |
| 22 |
packmol < step3_outerlayer.inp # This step builds the outer monolayer |
| 23 |
# It takes ~1-3 days |
| 24 |
|
| 25 |
|
| 26 |
# NOTE: PLEASE USE "packmol", NOT "ppackmol". ("ppackmol" is the |
| 27 |
# parallel-version of packmol using OpemMP. This example has NOT been |
| 28 |
# tested with "ppackmol". Our impression was that the "ppackmol" |
| 29 |
# version is more likely to get stuck in an infinite loop. -Andrew 2015-8) |