Changes between Version 2 and Version 3 of sherlock

Timestamp:

09/24/19 14:31:13 (5 years ago)

Author:

wchu28

Comment:

--

sherlock

@@ -6 +6 @@
 svn --username XXX --password XXX  checkout http://issm.ess.uci.edu/svn/issm/issm/trunk-jpl
 
+
+
+ == Installing ISSM on Sherlock  ==
+You need to install the following packages in this exact sequence:
+ - autotools (install.sh)
+ - petsc (install-3.9-sherlock.sh)
+ - m1qn3 (install.sh)
+
+Use the following configuration script (adapt to your needs):
+
+{{{
+#!sh
+./configure \
+ --prefix=$ISSM_DIR \
+ --with-wrappers=no \
+ --with-kml=no \
+ --with-bamg=no \
+ --with-metis-dir=$ISSM_DIR/externalpackages/metis/install \
+ --with-petsc-dir=$ISSM_DIR/externalpackages/petsc/install \
+ --with-m1qn3-dir=$ISSM_DIR/externalpackages/m1qn3/install \
+ --with-mpi-include="/data/apps/mpi/openmpi-1.8.3/gcc/4.8.3/include" \
+ --with-mpi-libflags="-L/data/apps/mpi/openmpi-1.8.3/gcc/4.8.3/lib -lmpi_cxx -lmpi -lmpi_usempi" \
+ --with-blas-lapack-dir=$ISSM_DIR/externalpackages/petsc/install \
+ --with-mumps-dir=$ISSM_DIR/externalpackages/petsc/install/ \
+ --with-scalapack-dir=$ISSM_DIR/externalpackages/petsc/install/ \
+ --with-numthreads=16 \
+ --with-fortran-lib="-L/data/apps/gcc/4.7.3/lib64 -lgfortran" \
+ --enable-debugging \
+ --enable-development
+}}}
+
+== sherlock_settings.m ==
+
+HPC staff ask that no "serious work" should be done on your home directory, you should create an execution directory as `/pub/$USERNAME/execution`.
+
+You have to add a file in `$ISSM_DIR/src/m` entitled `hpc_settings.m` with your personal settings on your local ism install:
+
+{{{
+#!m
+cluster.login='mmorligh';
+cluster.port=8000;
+cluster.queue='pub64';
+cluster.codepath='/data/users/mmorligh/trunk-jpl/bin/';
+cluster.executionpath='/data/users/mmorligh/trunk-jpl/execution/';
+}}}
+
+use your username for the `login` and enter your code path and execution path. These settings will be picked up automatically by matlab when you do `md.cluster=hpc()`
+
+== Running jobs on Sherlock  ==
+
+On hpc, you can use up to 64 cores per node. The more nodes and the longer the requested time, the more you will have to wait in the queue. So choose your settings wisely:
+
+ {{{
+#!m
+md.cluster=sherlock('numnodes',1,'cpuspernode',8);
+}}}
+
+The list of available queues is `'pub64','free64','free48','free*,pub64'` and `'free*'`.
+
+to have a job of 8 cores on one node. If the run lasts longer than 10 minutes, it will be killed and you will not be able to retrieve your results.
+
+Now if you want to check the status of your job and the queue you are using, type in the bash with the hpc session:
+
+ {{{
+#!sh
+qstat -u USERNAME
+}}}
+
+You can delete your job manually by typing:
+
+{{{
+#!sh
+qdel JOBID
+}}}
+
+where JOBID is the ID of your job (indicated in the Matlab session). Matlab indicates too the directory of your job where you can find the files `JOBNAME.outlog` and `JOBNAME.errlog`. The outlog file contains the informations that would appear if you were running your job on your local machine and the errlog file contains the error information in case the job encounters an error. 
+
+If you want to load results from the cluster manually (for example if you have an error due to an internet interruption), you find in the informations Matlab gave you `/home/srebuffi/trunk-jpl/execution//SOMETHING/JOBNAME.lock `, you copy the SOMETHING and you type in Matlab:
+
+{{{
+#!m
+md=loadresultsfromcluster(md,'SOMETHING');
+}}}
+
+