Difference between revisions of "Broadband Platform on HPCC"

From SCECpedia
Jump to navigationJump to search
Line 39: Line 39:
 
</pre>
 
</pre>
  
 +
It may be necessary to logout and login back again for these changes to be incorporated in the user environment (alternatively, users can source the changed file to force the changes to take effect immediately). To make sure the correct compilers are set up, users can type the following commands:
 +
 +
<pre>
 +
$ ifort --version
 +
ifort (IFORT) 10.0 20070426
 +
Copyright (C) 1985-2007 Intel Corporation.  All rights reserved.
 +
 +
$ gcc --version
 +
gcc (GCC) 4.3.3
 +
Copyright (C) 2008 Free Software Foundation, Inc.
 +
This is free software; see the source for copying conditions.  There is NO
 +
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
 +
</pre>
  
 
== Installing Desired Green's Functions and Validation Packages ==
 
== Installing Desired Green's Functions and Validation Packages ==

Revision as of 22:43, 25 September 2012

Current broadband studies may exceed 200K seismograms. To produce this number of seismograms, we need to use high performance computing.

Overview

In order to run the Broadband Platform on HPCC, users need to follow these steps:

  1. Installing and Building Broadband on HPCC
  2. Installing Desired Green's Functions and Validation Packages
  3. Configuring Required Environment Variables
  4. Creating Validation Runs
  5. Running Simulations

Broadband File System Issues

When running on HPCC, the validation scripts set up Broadband's BBP_DATA_DIR to use a directory in the /tmp filesystem. Because Broadband simulations are very I/O intensive, reading and writing thousands of small/medium files on an average simulation, we use a local filesystem on each compute node to minimize remote reads and writes and thus improve execution time. This approach also avoids creating a bottleneck a file server and eliminates unnecessary network traffic. It is therefore possible for multiple users to run their simulations on HPCC without significant interference.

Because the /tmp filesystem on each node is automatically cleaned at the end of each simulation, it is necessary to copy all wanted files to a permanent location. The HPCC validation scripts do that automatically after the simulations are finished (but before the PBS job ends).

Installing and Building BBP on HPCC

The first step in setting up the Broadband Platform on HPCC is to download and build the platform. Users should log into HPCC's hpc-login2.usc.edu head node and use the rcf-104 filesystem for their simulations. The rcf-104 filesystem is also mounted on the broadband.usc.edu server so it can be accessed from there as well. Depending on the shell employed, users will need too add the following lines in order to set up their environment:

csh -- add the following lines to the .cshrc file

# Setup for running broadband
source /usr/usc/gnu/gcc/default/setup.csh
source /usr/usc/intel/10.0/setup.csh
source /home/scec-00/opt/Python-2.6.2/setup.csh
source /usr/usc/matlab/default/setup.csh

bash -- add the following lines to the .bashrc file

# Setup for running broadband
source /usr/usc/gnu/gcc/default/setup.sh
source /usr/usc/intel/10.0/setup.sh
source /home/scec-00/opt/Python-2.6.2/setup.sh
source /usr/usc/matlab/default/setup.sh

It may be necessary to logout and login back again for these changes to be incorporated in the user environment (alternatively, users can source the changed file to force the changes to take effect immediately). To make sure the correct compilers are set up, users can type the following commands:

$ ifort --version
ifort (IFORT) 10.0 20070426
Copyright (C) 1985-2007 Intel Corporation.  All rights reserved.

$ gcc --version
gcc (GCC) 4.3.3
Copyright (C) 2008 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Installing Desired Green's Functions and Validation Packages

Configuring Required Environment Variables

Creating Validation Runs

Running Simulations