Changes between Version 18 and Version 19 of greenplanet

Timestamp:

05/10/16 16:20:22 (9 years ago)

Author:

jbondzio

Comment:

--

greenplanet

@@ -26 +26 @@
 
 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):
+You need to have a SSH public/private key pair. If you already have one, you can skip their creation described below. 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
@@ -49 +49 @@
 {{{
 #!sh
-$your_remosthost%cat ~/id_rsa.pub >> ~/.ssh/authorized_keys
-$your_remosthost%rm ~/id_rsa.pub
+$your_remotehost%cat ~/id_rsa.pub >> ~/.ssh/authorized_keys
+$your_remotehost%rm ~/id_rsa.pub
 }}}
 
@@ -69 +69 @@
 
 Greenplanet will ''only'' be used to run the code, you will use your local machine for pre and post processing, you will never use Greenplanet's matlab. You can check out ISSM and install the following packages:
- - autotools
+ - autotools (Greenplanet needs m4, so use install-discover.sh)
  - PETSc (use the greenplanet 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
@@ -119 +119 @@
 to have a maximum job time of 10 minutes and 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 Greeplanet session:
+Now if you want to check the status of your job and the queue you are using, type in the bash with the Greenplanet session:
 
  {{{
@@ -135 +135 @@
 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:
+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 `$ISSM_DIR/execution/LAUNCHSTRING/JOBNAME.lock `, you copy the LAUNCHSTRING and you type in Matlab:
 
 {{{
 #!m
-md=loadresultsfromcluster(md,'SOMETHING');
+md=loadresultsfromcluster(md,'LAUNCHSTRING');
 }}}