Running

After succesfully compiling the code, one has access to several executables. The main code for wave propagation simulations is:

[home dir]/quake/forward/psolve

Running Hercules entails executing psolve. How to actually get psolve running depends on the parallel engine and machine being used. The most simple way to run the program is in sequential mode. That is as simple as:

./psolve <input file>

On the other hand, running in parallel machine may require additional instructions. If using Open MPI or MPICH on a Mac or Linux computer, the executing command will look something like this:

./mpirun -n <num of pes> psolve <input file>

In more sophisticated supercomputers, the running command may look different and require some kind of scripts, but the basic principle is the same. Running in a Cray supercomputer like Kraken or Blue Waters, the final executing command may be similar to one of the following:

aprun -n <num of cores> psolve <input file>

aprun -n ${PBS_NNODES} psolve <input file>

aprun -B psolve <input file>

now, successfully running the program also requires to set up correctly the input file and a companion set of files and output directories.

The characteristics of the files may vary depending on the options given in the main input file provided in the command line. The main input file is traditionally called: parameters.in. A sample of the parameters.in is available Input Files page.

The following set up of files is the most commonly used. The running directory should have a copy of psolve and two main subdirectories, like this

[running dir]
drwxr-xr-x  5 user group 4.0K Jan  1 12:00 inputfiles/
drwxr-xr-x 11 user group 4.0K Jan  1 12:00 outputfiles/
-rwxr-xr-x  1 user group 7.0M Jan  1 12:00 psolve

The inputfiles directory should contain the parameters.in file and a subdirectory for the source files.

[inputfiles dir]
-rw-r--r--  1 user group 1.0K Jan  1 12:00 parameters.in
drwxr-xr-x  2 user group 4.0K Jan  1 12:00 sourcefiles/

And the outputfiles directory should have at least the following set of subdirectories.

[outpufiles dir]
drwxr-xr-x 2 user group 4.0K Jan  1 12:00 planes/
drwxr-xr-x 2 user group 4.0K Jan  1 12:00 srctmp/
drwxr-xr-x 2 user group 4.0K Jan  1 12:00 stations/

The content of the sourcefiles directory in the inputfiles directory may vary depending on the type of source model being used. For the most common option, srfh, the sourcefiles directory will have the following content:

[sourcefiles dir]
-rw-r--r-- 1 user group 1.0K Jan  1 12:00 area.in
-rw-r--r-- 1 user group 1.0K Jan  1 12:00 coords.in
-rw-r--r-- 1 user group 1.0K Jan  1 12:00 dip.in
-rw-r--r-- 1 user group 1.0K Jan  1 12:00 rake.in
-rw-r--r-- 1 user group 1.0K Jan  1 12:00 slipfunction.in
-rw-r--r-- 1 user group 1.0K Jan  1 12:00 slip.in
-rw-r--r-- 1 user group 1.0K Jan  1 12:00 source.in
-rw-r--r-- 1 user group 1.0K Jan  1 12:00 strike.in