Difference between revisions of "HowTo:autodock"

From CAC Wiki
Jump to: navigation, search
Line 4: Line 4:
  
 
{|  style="border-spacing: 8px;"
 
{|  style="border-spacing: 8px;"
| valign="top" width="50%" style="padding:1em; border:1px solid #aaaaaa; background-color:#e1eaf1; border-radius:7px" |
+
| valign="top" width="50%" style="padding:1em; border:1px solid #aaaaaa; background-color:#e1eaf1; border-radius:7px" |  
== General Overview ==
+
== Features ==
  
ADINA(Automatic Dynamic Incremental Non-linear Analysis) is a general-purpose finite element program for advanced engineering analysis in the fields of Structural Mechanics, Fluid Mechanics, Fluid-Structure Interactions, Heat Transfer, and Themomechanical Coupling.
+
NAMD 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.
  
The ADINA system consists of various programs that come with different tools and utilities that can be used independently or at once. In particular:
+
== Location of the program and setup ==
  
* '''0ADINA (adina8.5)''' for processing and analysis
+
The binary executable is in /opt/namd on the HPCVL Clusters. 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.
* '''ADINA User Interface (aui8.5)''' for pre-processing and post-processing (including geometry, mesh generation and analysis).
+
 
+
The present version of ADINA program is '''8.5.2'''
+
 
+
=== ADINA system ===
+
 
+
ADINA can run indiferently from the command line in interactive or batch mode, or through the <span>'''AUI'''</span> graphic interface.
+
 
+
Adina program has a large number of features and also Parallel Processing capabilities; as showed in this list of most important features:
+
 
+
==== Problems Solved ====
+
 
+
* Linear and Nonlinear structural analysis
+
* Dynamic analysis
+
* Thermal analysis of structures
+
* Buckling of structure
+
* Frequency analysis of structures
+
* Structural materials
+
* Heat Transfer
+
* Coupled Problems
+
* Multiphysics
+
* CFD including CFD Boundary conditions, and CFD Material models.
+
 
+
For more details check the information provided at the end of this document.
+
 
+
==== Solvers ====
+
 
+
* Frequency
+
** Sparse solver
+
* Large Models
+
** Iterative conjugate-gradient procedure with preconditioning
+
** GMRES with preconditioning
+
* Fluid Flows
+
** Iterative conjugate-gradient procedure
+
** Iterative procedures
+
** Bi-conjugate-gradient technique
+
* Multigrid
+
* Direct Skyline
+
* Explicit
+
** For ADINA-F only
+
 
+
For more details check the information provided at the end of this document.
+
 
+
==== Parallel Processing ====
+
 
+
ADINA also allows Parallel Processing (at the solver level only for SUN)
+
 
+
* Parallelization for:
+
** Calculation
+
** Assemblage of the element matrices
+
** Solution of the equations
+
** Calculation of the elements results
+
* NO pre-and post-processing with SUN Sparc architectures
+
* DDM is performed automatically
+
* Parallelization for:
+
** ADINA-F does not have paralellized assembly.
+
** ADINA and ADINA-T have paralellized assembly.
+
** 64-bit Equation solver(for problems demanding large size memory)
+
** 32-bit Porthole file.
+
 
+
For more details check the information provided at the end of this document.
+
 
+
==== Available tools ====
+
 
+
Moreover the '''adina''' and '''aui''' binaries, the ADINA system provides a set of shell scripts and utilities that allow the user to handle all aspects of running ADINA applications (located under '''$ADINAHOME/tools''')
+
 
+
The most important ones are:
+
 
+
* '''adina8.5''' Shell script program that controls most of ADINA programs.
+
* '''aui8.5''' Run the GUI and all demo examples.
+
 
+
And, the list of applications (programs) is:
+
 
+
* '''ADINA''' Structural Analysis $ADINAHOME/bin/adinat8.5
+
* '''ADINA-F''' Incompressible and fully compressible flows $ADINAHOME/bin/adina8.5
+
* '''ADINA-T''' Heat Transfer and field problems $ADINAHOME/adinat8.5
+
* '''ADINA-FSI''' Fluid flows with structural interactions $ADINAHOME/adfsi8.5
+
* '''ADINA-TMC''' Thermomechanical Coupling $ADINAHOME/adtmc8.5
+
* '''ADINA-M''' ADINA User interface with solid Modeling $ADINAHOME/aui8.5
+
* '''AUI''' ADINA User interface $ADINAHOME/aui8.5
+
 
+
==== Getting started using ADINA ====
+
 
+
Before starting you have to add the path to Adina binaries, scripts and libraries (namely '''PATH''' and '''LD_LIBRARY_PATH'''), to your environment variables.
+
For instance one must add the following line into his setup file (.profile, .bashrc, .cshrc, ...)
+
 
+
: '''$ use adina'''
+
 
+
Which takes care of all the ADINA setup, in particular the following directories:
+
 
+
: '''$ADINAHOME/bin''' ADINA home directorie
+
: '''$ADINAHOME/tools''' Shell scripts to run and maintain Adina programs
+
: '''$ADINAHOME/adina8.5''' Executable and shared libraries for general problems
+
: '''$ADINAHOME/adfsi8.5''' Executable and shared libraries for fluid-structure Interaction problems
+
: '''$ADINAHOME/adinat8.5''' Executable and shared libraries for heat transfer problems
+
: '''$ADINAHOME/adtmc8.5''' Executable and shared libraries for thermo-mechanical coupling problems
+
: '''$ADINAHOME/aui8.5''' Executable and shared libraries for Adina UI problems
+
 
+
The shared libraries are under '''$ADINAHOME/{ aui8.5, adfsi8.5, adina8.5, adinaf8.5, adinat8.5, adinatmc8.5, aui8.5, plugins, image, format }'''
+
 
+
Once done, ADINA system can be started either with the GUI '''aui8.5''' for interactive session, or with the '''adina''' program to run jobs from the command line.
+
  
 +
The setup for NAMD is very simple. It is only necessary type :
 +
<pre>use namd</pre>
 +
This will enter the proper directory into your PATH and off you go.
 
|}
 
|}
 
{|  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 ADINA ==
+
== Running NWChem from a command line==
  
=== Local Usage of Adina ===
+
NAMD requires a number of input files to run. These include:
 +
* A so-called "configuration file" that declares the initial configuration for a molecular dynamics run, the force field files, number of steps in the simulation, etc.
 +
* A coordinate file that gives the coordinates of the participating atoms or molecules.
 +
* A parameter file declaring bond-lengths, angles, dihedrals, non-bonded parameters etc.
 +
* A force-field file declaring parameters associated with atomic and molecular interactions.
 +
Details about the supported format of these input files can be found in the NAMD User's Guide.
  
On our systems, a user can only access Adina after they have filled in a [http://www.hpcvl.org/sites/default/files/adina-statement.pdf Adina User statement] (please fax to (613) 533-2015 or scan/email to [mailto:cac.admin@queensu.ca cac.admin@queensu.ca]. The statement is to the effect that the user  will abide by the licensing terms, namely by using the software for academic research purposes only.
+
NAMD supports several running modes. In the simplest case, it can be run in serial mode by typing:
 +
<pre>namd2 config_file</pre>
 +
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.
  
=== Interactive session with ADINA ===
+
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:
 +
<pre>namd2 +pN config_file</pre>
 +
if N threads are requested.
  
To enter the  '''ADINA'''  Graphical environment you must be logged in to a terminal or workstation that is running X-Windows and be sure that your '''DISPLAY''' environment variable is set for the terminal from which you are running X-windows; which should be the case if you are connecting through the portal.
+
== Submitting (parallel) NAMD jobs ==
  
If you log in from a '''UNIX''' machine using '''ssh''' then type:
+
Only short test jobs of application software can be run interactively on HPCVL machines. Production jobs must be submitted via the scheduling software Grid Engine. For usage of this software, please consult our [[FAQ:SGE|Grid Engine FAQ]].
  
: '''$ ssh -X -l hpcxxxx sfnode0.hpcvl.queensu.ca'''
+
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:
 
+
followed by
+
 
+
: '''$ ssh -X swlogin1'''
+
 
+
and then:
+
 
+
: '''$ use adina'''
+
 
+
To start the Graphic User Interface 'AUI' type:
+
 
+
: '''$ aui'''
+
 
+
which gives you the '''ADINA''' graphical window consisting of three major areas:
+
 
+
* Graphics Window
+
* Command Window
+
* Message Window
+
 
+
A '''HELP''' button is present at the top right of the GUI from where you can see a list of available documents and also information about demo examples.
+
 
+
To see all '''aui8.5''' input options type:
+
 
+
: '''$ aui8.5 -help'''
+
 
+
The most important ones are:
+
 
+
* '''-mm MMAX''' maximum memory for entire analysis
+
* '''-ms MSPARSE''' maximum memory for sparse solver
+
* '''-m MSTORE''' memory for matrix/element storage
+
* '''-t threads''' number of CPUs to use
+
* '''-ulimit''' remove limitation on all resources for this process
+
 
+
Users interested in using frequently ADINA should consult the specific chapters in the '''ADINA User’s Guide''' located under directory '''$ADINAHOME/docs'''
+
 
+
=== ADINA jobs from the command line ===
+
 
+
ADINA programs are controlled by a shell script named '''adina''' stored in the directory '''$ADINAHOME/tools'''
+
 
+
The shell script will submit and run your adina job, it has many input options. The minimun necessary to run a job is :
+
 
+
: '''$ adina job_name'''
+
 
+
Where '''job_name''' is the name of the job which must end with a '''.dat''' suffix.
+
 
+
Other options of interest to HPCVL users are:
+
 
+
: '''-u user''' use ser defined subroutine. The default is '''yes'''
+
: '''-t num''' Where 'num' is the number of threads. The default is '''one'''
+
: '''-nthread num''' Where 'num' is the number of threads for parallel matrix solver. The default is '''one'''
+
: '''-lib directory_name''' Where directory_name is the name of the directory where the job data I/O operations are done. The default is the current working directory.
+
: '''-m MTOT''' Amount of memory for use by program. For example, to specify 20 megabytes, use -m 20mb
+
: '''-in[fep]''' start in pre-processor mode
+
 
+
'''fep''' can be one of the following letters:
+
 
+
: '''A''' Pre-processing for ADINA Structures
+
: '''F''' Pre-processing for ADINA CFD
+
: '''T''' Pre-processing for ADINA Thermal
+
 
+
'''-plot''' start in post-processor mode
+
'''-cmd''' run in command mode
+
'''-s''' filename command file
+
'''-tools dir''' Directory for script to run ADINA solutions. Default is '''$ADINAHOME/tools'''
+
'''-tmp dir''' Directory for temporary files. Default is '''/hpcxxxx/scratch'''
+
'''-ma''' Maxsize Parameter, overrides value given in include file. The default '''NORMAL''' number is 20 Mbyte, and the maximum amount of memory '''MAXSIZE''' to allocate is 4Gbyte.
+
 
+
 
+
'''Note.''' ADINA manages the memory dynamically, so in most cases you will not have to use this option.
+
 
+
=== Batch ADINA jobs ===
+
 
+
As indicated above the '''adina''' utility script allow the user to run adina jobs in batch mode, which can be used without any other option in the process of developing and debugging your ADINA applications.
+
 
+
By default '''adina''' will run the job in background and in order to avoid input verification before starting the job add the ''''-v no'''' option.
+
For example, if the name of adina job is 'cyl2.dat' (look at the examples in one of these directories '''$ADINAHOME/examples''' or '''$ADINAHOME''' one may type:
+
 
+
: '''$ adina -j cyl2'''
+
 
+
or also, if you are using your own user defined subroutine '''user.f''' with ADINA, you can type:
+
 
+
: '''$ adina -j cyl2 -u user'''
+
 
+
'''Note'''. Once your job is ready for production, you should use instead the Grid Engine job management system to run and manage your ADINA jobs, (see next section).
+
 
+
|}
+
{|  style="border-spacing: 8px;"
+
| valign="top" width="50%" style="padding:1em; border:1px solid #aaaaaa; background-color:#e1eaf1; border-radius:7px" |
+
 
+
== ADINA jobs with Grid Engine  ==
+
 
+
=== Submitting sequential ADINA jobs through Grid Engine ===
+
 
+
Before starting we refer users to our HPCVL Grid Engine FAQ for more details about the usage of Grid Engine on HPCVL machines.
+
 
+
Submitting a sequential adina job to Grid Engine queues is the same as submitting any sequential job. But users must make sure that there is no interaction between the program and them, and also note that you can not run the '''adina GUI''' program through Grid Engine.
+
 
+
Here is some basic steps you should follow in order to submit your job:
+
 
+
* All the data required to run the job must be collected in the command file '''job_name.in''' (created by '''AUI''').
+
* If submitting a batch job use '''adina''' or '''adina -cmd'''
+
* You may also need to give the full pathname of '''adina''' shell script if your environment variables are not exported.
+
 
+
After this, the executable line in your Grid Engine batch script should look like this:
+
 
+
: '''$ adina job_name'''
+
 
+
and then you can add other Grid Engine general options like mail notification or name of the job, etc ...
+
 
+
A full example of Adina sequential job with Grid Engine can be found here:
+
  
 
<pre>
 
<pre>
#!/bin/sh
+
#!/bin/bash
# This is a simple example of a GE batch script for adina
+
# request Bourne again shell as shell for job
+
 
#$ -S /bin/bash
 
#$ -S /bin/bash
# name of the job
+
#$ -q abaqus.q
#$ -N baseline
+
#$ -l qname=abaqus.q
# export environment variables
+
 
#$ -V
 
#$ -V
# Joining standard output and error into a specified file
 
#$ -j y
 
 
#$ -cwd
 
#$ -cwd
# run adina job
+
#$ -M {email address}
adina8.5 -R 3000MB cyl2
+
#$ -m be
 +
#$ -o {screen output file}
 +
#$ -e {screen error file}
 +
#$ -pe shm.pe {number of threads}
 +
namd2 +p$NSLOTS {namd configuration (input) file}
 
</pre>
 
</pre>
  
Once your Grid Engine script for '''ADINA''' (let’s call it '''adina_seq.sh''') is ready you can submit it to Grid Engine:
+
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.
  
: '''$ qsub adina_seq.sh'''
+
"#$ -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.
  
=== Submitting parallel adina jobs through Grid Engine ===
+
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.
  
ADINA system has parallel processing capabilities based on domain decomposition techniques. It’s available on shared and distributed machines using multithreading for communications between the processes, while the parallel performance of the solver is done using multithreading.
+
Once you have a proper script file (let's call it namd.sh) you can submit your production job by typing
  
Note that most features of ADINA are also available within the parallel framework (to see if your adina application can run in parallel take a look at '''ADINA Release notes''' or contact HPCVL support team.
+
<pre>qsub namd.sh</pre>
  
For a parallel job, moreover the conditions discussed in the previous section concerning sequential adina job with Grid Engine, you need to specify the number of processors to be used. This is done with two options of the '''adina''' script
+
The Grid Engine will take care of the rest.
 
+
# '''adina -t num''' where 'num' is the number of processors, usually it’s the same as the number of subdomains, and the 'adina' program will split the hole domain to 'num' subdomains. Note that you can use 'aui8.5' to view the results in the hole domain or in any of the subdomaines.
+
# '''adina -thread num''', where 'num' is the number of threads for parallel matrix solver only. (Note. This is used automatically in the case of parallel DDM jobs).
+
 
+
The command line in your Grid Engine batch script should look like this:
+
 
+
: '''adina -j job_name'''
+
 
+
If you are interested in parallelizing the matrix solver only you can use this line:
+
 
+
: '''adina -t num -j job_name'''
+
 
+
A full example of Adina parallel job with Grid Engine can be found here:
+
 
+
<pre>
+
#!/bin/sh
+
# This is a simple example of a GE batch script for adina
+
# request Bourne again shell as shell for job
+
#$ -S /bin/bash
+
# name of the job
+
#$ -N baseline
+
# export environment variables
+
#$ -V
+
# Joining standard output and error into a specified file
+
#$ -j y
+
#$ -cwd
+
# Request of the multithreading parallel environment
+
#$ -pe shm.pe 4
+
#$ -v PARALLEL=4
+
#$ -v OMP_NUM_THREADS=4
+
# make sure <number_of_processors> is the same as above
+
# run adina job
+
adina8.5 -R 3000MB -t 4 cyl2
+
</pre>
+
 
+
Once your Grid Engine script for Adina (let’s call it '''adina_par.sh''') is ready you can submit is through to Grid Engine:
+
 
+
: '''$ qsub adina_par.sh'''
+
  
 
|}
 
|}
 
{|  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:#e1eaf1; border-radius:7px" |
==  Help and Documentation ==
+
 
+
A lot of ADINA specific documentation and examples can be found at [http://www.adina.com/support http://www.adina.com/support]
+
  
The set of ADINA system online manuals documentation (in PDF) is under the directory '''$ADINAHOME/doc'''.
+
== Licensing ==
 +
NAMD 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 exists between the University of Illinois and HPCVL, and to [http://www.hpcvl.org/sites/default/files/hpvcl_namd_statement.pdf 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.
  
HPCVL users will find the follwoing documents:
+
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 Information ==
* '''ADINA User Interface Command Reference Manual:'''
+
** '''Volume I: Solids and Structures'''
+
** '''Volume II: Heat Transfer'''
+
** '''Volume III: CFD and FSI'''
+
** '''Volume IV: Display Processing'''
+
* '''ADINA Theory and Modeling Guides:'''
+
** '''Volume I: Solids and Structures'''
+
** '''Volume II: Heat Transfer'''
+
** '''Volume III: CFD and FSI'''
+
* '''ADINA User Interface Primer Guide'''
+
* '''ADINA verification Manual'''
+
* '''ADINA Nastran Interface'''
+
* Under the '''$ADINAHOME/samples''' directory you will find the set of problems accompagning the training and also the introductory courses.
+
* Under the '''$ADINAHOME/docs''' directory you will find the '''Adina User’s Guide'''.
+
  
You can also access the '''HELP''' menu from the ADINA GUI, from where you get the list of all '''PRODUCT DOCUMENTATION''' and also a possibility to run '''DEMONSTRATION''' problems.
+
NAMD requires practice to be used efficiently. We cannot explain it use in any detail here, but
  
HPCVL also offers user support; for questions about this FAQ and usage of ADINA software on HPCVL machines, [[Contacts:UserSupport|contact us]] or send an email to : '''help@hpcvl.org'''
+
* Complete documentation for the program is available in the form of the [http://www.ks.uiuc.edu/Research/namd/documentation.html User's Guide], which is an absolute must-have if you want to use this program.
 +
* Check out the [http://www.ks.uiuc.edu/Research/namd/ NAMD website]. They feature a very useful FAQ and even a tutorial.
 +
* There is an active [http://www.ks.uiuc.edu/Research/namd/mailing_list/ NAMD Mailing List].
 +
* '''Send [mailto:cac.help@queensu.ca|email to cac.help@queensu.ca]'''. We're happy to help.
 
|}
 
|}

Revision as of 13:51, 15 June 2016

AutoDock

This is a short help file on the AutoDock suite of automated docking tools. This software allows the prediction of how small molecules bind to a receptor site of known structure. Since AutoDock is a rather sophisticated set of tools, this FAQ cannot replace the manual. It is rather meant as a starting point for using AutoDock, and to answer questions that are specific to our installation of the software.

Features

NAMD 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 setup

The binary executable is in /opt/namd on the HPCVL Clusters. 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 line

NAMD requires a number of input files to run. These include:

  • A so-called "configuration file" that declares the initial configuration for a molecular dynamics run, the force field files, number of steps in the simulation, etc.
  • A coordinate file that gives the coordinates of the participating atoms or molecules.
  • A parameter file declaring bond-lengths, angles, dihedrals, non-bonded parameters etc.
  • A force-field file declaring parameters associated with atomic and molecular interactions.

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 jobs

Only short test jobs of application software can be run interactively on HPCVL 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.

Licensing

NAMD 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 exists between the University of Illinois and HPCVL, 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 Information

NAMD requires practice to be used efficiently. We cannot explain it use in any detail here, but

  • Complete documentation for the program is available in the form of the User's Guide, which is an absolute must-have if you want to use this program.
  • Check out the NAMD website. They feature a very useful FAQ and even a tutorial.
  • There is an active NAMD Mailing List.
  • Send to cac.help@queensu.ca. We're happy to help.