Home > Documentation > Software >autodock_vina

autodock_vina

Versions and Availability

▶ Display Module Names for autodock_vina on all clusters.

Machine Version Module
None Available N/A N/A

▶ Module FAQ?

The information here is applicable to LSU HPC and LONI systems.

h4

Shells

A user may choose between using /bin/bash and /bin/tcsh. Details about each shell follows.

/bin/bash

System resource file: /etc/profile

When one access the shell, the following user files are read in if they exist (in order):

  1. ~/.bash_profile (anything sent to STDOUT or STDERR will cause things like rsync to break)
  2. ~/.bashrc (interactive login only)
  3. ~/.profile

When a user logs out of an interactive session, the file ~/.bash_logout is executed if it exists.

The default value of the environmental variable, PATH, is set automatically using Modules. See below for more information.

/bin/tcsh

The file ~/.cshrc is used to customize the user's environment if his login shell is /bin/tcsh.

Modules

Modules is a utility which helps users manage the complex business of setting up their shell environment in the face of potentially conflicting application versions and libraries.

Default Setup

When a user logs in, the system looks for a file named .modules in their home directory. This file contains module commands to set up the initial shell environment.

Viewing Available Modules

The command

$ module avail

displays a list of all the modules available. The list will look something like:

--- some stuff deleted ---
velvet/1.2.10/INTEL-14.0.2
vmatch/2.2.2

---------------- /usr/local/packages/Modules/modulefiles/admin -----------------
EasyBuild/1.11.1       GCC/4.9.0              INTEL-140-MPICH/3.1.1
EasyBuild/1.13.0       INTEL/14.0.2           INTEL-140-MVAPICH2/2.0
--- some stuff deleted ---

The module names take the form appname/version/compiler, providing the application name, the version, and information about how it was compiled (if needed).

Managing Modules

Besides avail, there are other basic module commands to use for manipulating the environment. These include:

add/load mod1 mod2 ... modn . . . Add modules
rm/unload mod1 mod2 ... modn  . . Remove modules
switch/swap mod . . . . . . . . . Switch or swap one module for another
display/show  . . . . . . . . . . List modules loaded in the environment
avail . . . . . . . . . . . . . . List available module names
whatis mod1 mod2 ... modn . . . . Describe listed modules

The -h option to module will list all available commands.

▶ Did not find the version you want to use??

If a software package you would like to use for your research is not available on a cluster, you can request it to be installed. The software requests are evaluated by the HPC staff on a case-by-case basis. Before you send in a software request, please go through the information below.

h3

Types of request

Depending on how many users need to use the software, software requests are divided into three types, each of which corresponds to the location where the software is installed:

  • The user's home directory
    • Software packages installed here will be accessible only to the user.
    • It is suitable for software packages that will be used by a single user.
    • Python, Perl and R modules should be installed here.
  • /project
    • Software packages installed in /project can be accessed by a group of users.
    • It is suitable for software packages that
      • Need to be shared by users from the same research group, or
      • are bigger than the quota on the home file syste.
    • This type of request must be sent by the PI of the research group, who may be asked to apply for a storage allocation.
  • /usr/local/packages
    • Software packages installed under /usr/local/packages can be accessed by all users.
    • It is suitable for software packages that will be used by users from multiple research groups.
    • This type of request must be sent by the PI of a research group.

h3

How to request

Please send an email to sys-help@loni.org with the following information:

  • Your user name
  • The name of cluster where you want to use the requested software
  • The name, version and download link of the software
  • Specific installation instructions if any (e.g. compiler flags, variants and flavor, etc.)
  • Why the software is needed
  • Where the software should be installed (locally, /project, or /usr/local/packages) and justification explaining how many users are expected.

Please note that, once the software is installed, testing and validation are users' responsibility.

About the Software

Description Path: key[@id="autodock_vina"]/whatis Not Found!

Usage

AutoDock Vina can use multiple cores in computation by adding --cpu arg .


The usage summary can be obtained with "vina --help":

Input:
 --receptor arg        rigid part of the receptor (PDBQT)
 --flex arg            flexible side chains, if any (PDBQT)
 --ligand arg          ligand (PDBQT)

Search space (required):
 --center_x arg	       X coordinate of the center
 --center_y arg        Y coordinate of the center
 --center_z arg        Z coordinate of the center
 --size_x arg          size in the X dimension (Angstroms)
 --size_y arg          size in the Y dimension (Angstroms)
 --size_z arg          size in the Z dimension (Angstroms)

Output (optional):
 --out arg	output models (PDBQT), the default is chosen based 
		the ligand file name
 --log arg      optionally, write log file

Misc (optional):
 --cpu arg      the number of CPUs to use (the default is to try to
                detect the number of CPUs or, failing that, use 1)
 --seed arg     explicit random seed
 --exhaustiveness arg (=8) exhaustiveness of the global search (roughly 
                  proportional to time): 1+
 --num_modes arg (=9)     maximum number of binding modes to generate
 --energy_range arg (=3)  maximum energy difference between the best binding 
                          mode and the worst one displayed (kcal/mol)

Configuration file (optional):
 --config arg    the above options can be put here

Information (optional):
 --help            display usage summary
 --help_advanced   display usage summary with advanced options
 --version         display program version

For convenience, some command line options can be placed into a configuration file.
e.g.
    receptor = hsg1/rigid.pdbqt
    ligand = ligand.pdbqt
    center_x =  2
    center_y =  6
    center_z = -7
    size_x = 25
    size_y = 25
    size_z = 25
    energy_range = 4

Resources

Last modified: September 10 2020 11:58:50.