Skip to main content

piny

About

PINY_MD is a molecular dynamics simulation tool.

Versions and Availability

▶ Display Softenv Keys for piny all clusters
Machine Version Softenv Key
eric Aug 30 2005 +piny-md-intel-11.1-mvapich-1.1
qb Aug 30 2005 +piny-md-intel-11.1-mvapich-1.1
oliver Aug 30 2005 +piny-md-intel-11.1-mvapich-1.1
louie Aug 30 2005 +piny-md-intel-11.1-mvapich-1.1
poseidon Aug 30 2005 +piny-md-intel-11.1-mvapich-1.1
painter Aug 30 2005 +piny-md-intel-11.1-mvapich-1.1
▶ Softenv FAQ?

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

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 SoftEnv. 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.

Softenv

SoftEnv is a utility that is supposed to help users manage complex user environments with potentially conflicting application versions and libraries.

System Default Path

When a user logs in, the system /etc/profile or /etc/csh.cshrc (depending on login shell, and mirrored from csm:/cfmroot/etc/profile) calls /usr/local/packages/softenv-1.6.2/bin/use.softenv.sh to set up the default path via the SoftEnv database.

SoftEnv looks for a user's ~/.soft file and updates the variables and paths accordingly.

Viewing Available Packages

The command softenv will provide a list of available packages. The listing will look something like:

$ softenv
These are the macros available:
*   @default
These are the keywords explicitly available:
+amber-8                       Applications: 'Amber', version: 8 Amber is a
+apache-ant-1.6.5              Ant, Java based XML make system version: 1.6.
+charm-5.9                     Applications: 'Charm++', version: 5.9 Charm++
+default                       this is the default environment...nukes /etc/
+essl-4.2                      Libraries: 'ESSL', version: 4.2 ESSL is a sta
+gaussian-03                   Applications: 'Gaussian', version: 03 Gaussia
... some stuff deleted ...
Managing SoftEnv

The file ~/.soft in the user's home directory is where the different packages are managed. Add the +keyword into your .soft file. For instance, ff one wants to add the Amber Molecular Dynamics package into their environment, the end of the .soft file should look like this:

+amber-8

@default

To update the environment after modifying this file, one simply uses the resoft command:

% resoft

The command soft can be used to manipulate the environment from the command line. It takes the form:

$ soft add/delete +keyword

Using this method of adding or removing keywords requires the user to pay attention to possible order dependencies. That is, best results require the user to remove keywords in the reverse order in which they were added. It is handy to test out individual keys, but can lead to trouble if changing multiple keys. Changing the .soft file and issuing the resoft is the recommended way of dealing with multiple changes.

▶ Display Module Names for piny on all clusters.
Machine Version Module
▶ Module FAQ?

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

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 SoftEnv. 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.

Module is currently available only on SuperMIC.

Usage

Usage requires invoking the PINY_MD command and providing it with the name of an input file as an argument. Generically, it looks like:

    $ piny_md_machine sim_input
  

To find the name assigned to the executable, use the soft-dbq to examine the softenv key used for PINY. It will give the path to executable. For instance:

$ soft-dbq +piny-md-intel-11.1-mvapich-1.1
     
This is all the information associated with
the key or macro +piny-md-intel-11.1-mvapich-1.1.

-------------------------------------------

Name: +piny-md-intel-11.1-mvapich-1.1
Description: @types: Applications @name: piny-md @version: Aug 30,
2005 @build: mvapich-1.1-intel-10.1 @about: PINY_MD(c) is a
multipurpose, object-oriented molecular simulation package developed
as a collaborative effort between Indiana University, New York
University and the University of Pennsylvania.
Flags: none
Groups: none
Exists on: Linux

-------------------------------------------

On the Linux architecture,
the following will be done to the environment:

  The following environment changes will be made:
    PATH = ${PATH}:/usr/local/packages/piny-md/intel-11.1-mvapich-1.1/bin
$ ls /usr/local/packages/piny-md/intel-11.1-mvapich-1.1/bin
piny_md_par

This shows the path to PINY_MD and the existance of a single executable name piny_md_par. The _par indicates it is a parallel build, and the key name shows it was built with mvapich 1.1.

Setting up a simulation is the hard part of using the program. For guidance there, please refer to the Resources below.

Resources

Last modified: November 14 2014 10:23:42.