Difference between revisions of "HowTo:namd"
(→Licensing) |
(→Location of the program and setup) |
||
Line 11: | Line 11: | ||
== Location of the program and setup == | == Location of the program and setup == | ||
− | The binary executable is in /opt/namd | + | The binary executable is in /opt/namd. The present version of the program is 2.10, and it is available on the Linux platform in its 64 bit version. Therefore, all the relevant executables are in /opt/namd/2.10. Documentation can be found at the main NAMD site and a simple example (Alanin) is in /opt/namd/2.10/example. |
The setup for NAMD is very simple. It is only necessary type : | The setup for NAMD is very simple. It is only necessary type : | ||
Line 18: | Line 18: | ||
|} | |} | ||
{| style="border-spacing: 8px;" | {| style="border-spacing: 8px;" | ||
− | | valign="top" width="50%" style="padding:1em; border:1px solid #aaaaaa; background-color:#f7f7f7; border-radius:7px" | | + | | valign="top" width="50%" style="padding:1em; border:1px solid #aaaaaa; background-color:#f7f7f7; border-radius:7px" | |
== Running NWChem from a command line== | == Running NWChem from a command line== |
Revision as of 13:54, 31 March 2017
Contents
NAMD
This is a quick introduction to the usage of the free but licensed code NAMD2 that is installed on our clusters. It is meant as an initial pointer to more detailed information and a Getting Started primer. It does not replace study of the manual.
FeaturesNAMD is a parallel code for molecular dynamics simulation of large biomolecular systems, developed by the Theoretical Biophysics Group ("TBG") in the Beckman Institute of the University of Illinois . It is file-compatible with AMBER, CHARMM, and X-PLOR. Location of the program and setupThe binary executable is in /opt/namd. The present version of the program is 2.10, and it is available on the Linux platform in its 64 bit version. Therefore, all the relevant executables are in /opt/namd/2.10. Documentation can be found at the main NAMD site and a simple example (Alanin) is in /opt/namd/2.10/example. The setup for NAMD is very simple. It is only necessary type : use namd This will enter the proper directory into your PATH and off you go. |
Running NWChem from a command lineNAMD requires a number of input files to run. These include:
Details about the supported format of these input files can be found in the NAMD User's Guide. NAMD supports several running modes. In the simplest case, it can be run in serial mode by typing: namd2 config_file where config_file is the configuration input file mentioned above. It is recommended to give the configuration file the file extension .namd to enable consistent naming of the output files. These will be generated automatically, and the progress of the program run will be tracked on the screen. NAMD is also able to run in parallel mode. For our shared-memory systems, it is easiest to run it by specifying the number of threads through the +p option: namd2 +pN config_file if N threads are requested. Submitting (parallel) NAMD jobsOnly short test jobs of application software can be run interactively on our machines. Production jobs must be submitted via the scheduling software Grid Engine. For usage of this software, please consult our Grid Engine FAQ. In most cases, you will be running NAMD production jobs in parallel mode. This means that you need to specify a number of CPUs that should be reserved to run each independent NAMD thread. This is done in a Grid Engine submission script: #!/bin/bash #$ -S /bin/bash #$ -q abaqus.q #$ -l qname=abaqus.q #$ -V #$ -cwd #$ -M {email address} #$ -m be #$ -o {screen output file} #$ -e {screen error file} #$ -pe shm.pe {number of threads} namd2 +p$NSLOTS {namd configuration (input) file} The items in the template that are enclosed in {} be replaced by the appropriate values. Lines that start with "#$" contain information for Grid Engine. The "#$ -V" line tells GE to inherit the shell setup from the calling shell, for instance the $PATH variable. It is important to remember that you need to set up NAMD by issuing the "use namd" command before submitting the above script. "#$ -cwd" tells the system to start from the current working directory. "#$ -M" lets the system know you email address, so it can notify you when the job starts and ends. The "#$ -o" and "#$ -e" lines are there to define files that capture output that would go to the screen in an interactive run, coming from the program and the system, repsectively. Finally, the "#$ -pe" line serves to define the number of CPUs to be reserved. The number you insert here will be reused through the environment variable $NSLOTS, so that you do not have to type it again in the namd2 command line. Note that the name of the configuration file that replaces "configuration file" in the script template, should have file extension .namd, just as in the interactive run. Once you have a proper script file (let's call it namd.sh) you can submit your production job by typing qsub namd.sh The Grid Engine will take care of the rest. |
LicensingNAMD is free for non-commercial use, but it is licensed. As with other licensed software, we ask our users to read through the license agreement that we have with the University of Illinois, and to sign a statement that they agree to abide by the terms of the license. The main issue in the NAMD case is that usage has to non-commercial. Once we have received the signed statement (FAX to (613) 533-2015 or scan/email to admin@hpcvl.org), we will enter the user to a Unix group namd which enables access to the software. More InformationNAMD requires practice to be used efficiently. We cannot explain it use in any detail here, but
|