Skip to content

Commit 63acb7e

Browse files
authored
Merge pull request #246 from maflister/add-namd
Add NAMD guide
2 parents fbd1152 + 5de8f87 commit 63acb7e

File tree

2 files changed

+84
-0
lines changed

2 files changed

+84
-0
lines changed

docs/software/namd.md

Lines changed: 83 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,83 @@
1+
# NAMD
2+
3+
NAMD is a parallel molecular dynamics code designed for simulation of large biomolecular systems.
4+
5+
## NAMD2 or NAMD3
6+
7+
NAMD3 was recently released and is installed on the cluster. The command options and syntax may be different from NAMD2 and it is up to the user to decide the appropriate version.
8+
9+
To list available NAMD versions:
10+
11+
=== "NAMD2"
12+
```txt
13+
module avail namd2
14+
15+
------------------------------------------------------------ /hpc/modulefiles -------------------------------------------------------------
16+
namd2/2.14-cuda-mpi namd2/2.14-mpi namd2/2.14 (D)
17+
```
18+
19+
=== "NAMD3"
20+
```txt
21+
module avail namd3
22+
23+
------------------------------------------------------------ /hpc/modulefiles -------------------------------------------------------------
24+
namd3/3.0.1-cuda namd3/3.0.1 (D)
25+
```
26+
27+
Several versions are installed including parallel (mpi) and GPU (cuda) enabled options. The default module marked with `(D)` should be used in most cases for single-node simulations up to 48 cores.
28+
29+
To load NAMD in a job script:
30+
31+
=== "NAMD2"
32+
```txt
33+
module load namd2/2.14
34+
```
35+
36+
=== "NAMD3"
37+
```txt
38+
module load namd3/3.0.1
39+
```
40+
41+
Remember to adjust the version of NAMD required for your type of simulation.
42+
43+
## Batch job
44+
45+
To run NAMD in a batch job, first create a job script.
46+
47+
=== "namd2-job.slurm"
48+
```txt
49+
#!/bin/bash
50+
#SBATCH --job-name=single-node
51+
#SBATCH --ntasks=1
52+
#SBATCH --cpus-per-task=8
53+
#SBATCH --time=72:00:00
54+
55+
module load namd2/2.14
56+
57+
## Single node.
58+
## This will start a simulation on 8 CPU cores with 72 hour time
59+
## limit. If you want to increase the number of CPU cores, adjust
60+
## the cpus-per-task parameter above. You need to update the namd
61+
## config and log output file names to suit your simulation.
62+
63+
namd2 +p$SLURM_CPUS_PER_TASK +idlepoll namd_config_file.conf > namd_run_1.log
64+
```
65+
66+
=== "namd3-job.slurm"
67+
```txt
68+
#!/bin/bash
69+
#SBATCH --job-name=single-node
70+
#SBATCH --ntasks=1
71+
#SBATCH --cpus-per-task=8
72+
#SBATCH --time=72:00:00
73+
74+
module load namd3/3.0.1
75+
76+
## Single node.
77+
## This will start a simulation on 8 CPU cores with 72 hour time
78+
## limit. If you want to increase the number of CPU cores, adjust
79+
## the cpus-per-task parameter above. You need to update the namd
80+
## config and log output file names to suit your simulation.
81+
82+
namd3 +p$SLURM_CPUS_PER_TASK +idlepoll namd_config_file.conf > namd_run_1.log
83+
```

mkdocs.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -177,6 +177,7 @@ nav:
177177
- software/conda.md
178178
- software/lsdyna.md
179179
- software/matlab.md
180+
- software/namd.md
180181
- software/nextflow.md
181182
- software/python.md
182183
- software/pytorch.md

0 commit comments

Comments
 (0)