Changes between Version 2 and Version 3 of lonestar

Timestamp:

09/17/15 19:22:22 (9 years ago)

Author:

seroussi

Comment:

--

lonestar

@@ -9 +9 @@
 Host lonestar lonestar.tacc.utexas.edu
    HostName lonestar.tacc.utexas.edu
-  User YOURHPCUSERNAME
+  User YOURUSERNAME
   HostKeyAlias lonestar.tacc.utexas.edu
   HostbasedAuthentication no
 }}}
-and replace `YOURHPCUSERNAME` by your lonestar username.
+and replace `YOURUSERNAME` by your lonestar username.
 
 Once this is done, you can ssh lonestar by simply doing:
@@ -24 +24 @@
 == 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. 
+Once you have the account, you can setup a public key authentication 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):
 {{{
@@ -95 +95 @@
 }}}
 
-
-== STOP HERE ==
-
 == lonestar_settings.m ==
 
@@ -105 +102 @@
 #!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/';
+cluster.codepath='/home1/03729/seroussi/trunk-jpl/bin/';
+cluster.executionpath='/home1/03729/seroussi/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()`
+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=lonestar()`
 
-== Running jobs on hpc  ==
+== Running jobs on lonestar  ==
 
-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:
+On lonestar, each node has 12 cores and you can use any multiple of 12 for the total number of processors. 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);
+md.cluster=lonestar('numnodes',2);
 }}}
 
-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.
+to have a job of 2 nodes, 12 cpus for nodes, so a total of 24 cores.
 
-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:
+Now if you want to check the status of your job and the queue you are using, type in the bash with the lonestar session:
 
  {{{