Changes between Initial Version and Version 1 of lonestar

Timestamp:

09/17/15 13:47:18 (9 years ago)

Author:

seroussi

Comment:

--

lonestar

@@ +1 @@
+== Getting an account ==
+
+more to come...
+== ssh configuration ==
+
+You can add the following lines to `~/.ssh/config` on your local machine:
+{{{
+#!sh
+Host lonestar lonestar.tacc.utexas.edu
+   HostName lonestar.tacc.utexas.edu
+  User YOURHPCUSERNAME
+  HostKeyAlias lonestar.tacc.utexas.edu
+  HostbasedAuthentication no
+}}}
+and replace `YOURHPCUSERNAME` by your lonestar username.
+
+Once this is done, you can ssh lonestar by simply doing:
+
+{{{
+#!sh
+ssh lonestar
+}}}
+
+== Password-less ssh ==
+
+Once you have the account, you can setup a public key authentification in order to avoid having to input your password for each run. 
+You need to have a SSH public/private key pair. If you do not, you can create a SSH public/private key pair by typing the following command and following the prompts (no passphrase necessary):
+{{{
+#!sh
+$your_localhost% ssh-keygen -t rsa
+Generating public/private rsa key pair.
+Enter file in which to save the key (/Users/username/.ssh/id_rsa):RETURN
+Enter passphrase (empty for no passphrase):RETURN
+Enter same passphrase again:RETURN
+Your identification has been saved in /Users/username/.ssh/id_rsa.
+Your public key has been saved in /Users/username/.ssh/id_rsa.pub.
+}}}
+
+Two files were created: your private key `/Users/username/.ssh/id_rsa`, and the public key `/Users/username/.ssh/id_rsa.pub`. The private key is read-only and only for you, it is used to decrypt all correspondence encrypted with the public key. The contents of the public key need to be copied to `~/.ssh/authorized_keys` on your lonestar account:
+
+{{{
+#!sh
+$your_localhost%scp ~/.ssh/id_rsa.pub username@your_remosthost:~
+}}}
+
+Now on '''lonestar''', copy the content of id_rsa.pub:
+
+{{{
+#!sh
+$your_remosthost%cat ~/id_rsa.pub >> ~/.ssh/authorized_keys
+$your_remosthost%rm ~/id_rsa.pub
+}}}
+
+== Environment ==
+
+On lonestar, add the following lines to `~/.bash_login`:
+{{{
+#!sh
+export ISSM_DIR=PATHTOTRUNK
+source $ISSM_DIR/etc/environment.sh
+module load cmake/2.8.7
+module load mkl/10.3
+}}}
+
+''Log out and log back in'' to apply this change.
+
+== STOP HERE ==
+
+== Installing ISSM on lonestar ==
+
+lonestar will ''only'' be used to run the code, you will use your local machine for pre and post processing, you will never use lonestar's matlab. You can check out ISSM and install the following packages:
+ - autotools
+ - PETSc (use the hpc script and ``follow`` the instructions, you will need to submit a job and compile PETSc manually, do not make test, it will not work on the cluster)
+ - m1qn3
+
+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" \
+ --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
+}}}
+== lonestar_settings.m ==
+
+You have to add a file in `$ISSM_DIR/src/m` entitled `lonestar_settings.m` with your personal settings on your local ism install:
+
+{{{
+#!m
+cluster.login='seroussi';
+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 hpc  ==
+
+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=hpc('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.