Changes between Version 5 and Version 6 of pace

Timestamp:

01/13/21 08:42:57 (4 years ago)

Author:

arobel

Comment:

--

pace

@@ -29 +29 @@
 (d) An output text file should be created in the same directory as the batch file. You can have a quick look at the status of the run (which ISSM should output) using vi or less.
 
-2. For other non-test ISSM runs, the batch script should generally look like:<br />
+2. For other non-test ISSM runs, the batch script should generally look like:
 ------
 #PBS -N JOBNAME [[BR]]
@@ -69 +69 @@
 2. The build script is organized into "batches". To build the packages and source code in the correct order, simply go through the build script and uncomment one batch at a time and then run the script (using the command ./build-with-mvapich.sh after uncommenting each batch individually).
 
-3. If you are modifying source code and have previously built ISSM locally successfully, you should only need to run batch 6 which simply compiles the source code (and doesn't recompile all the dependencies).
+3. Once you've successfully built ISSM, the batch script will look slightly different:
+------
+#PBS -N JOBNAME [[BR]]
+#PBS -A GT-arobel3-atlas[[BR]] 
+#PBS -o output.$PBS_JOBID[[BR]]
+#PBS -j oe[[BR]]
+#PBS -l nodes=NNODES:ppn=NPROC[[BR]]
+#PBS -l walltime=DAYS:HOURS:MINS:00[[BR]]
+
+ISSMROOT=$PBS_O_WORKDIR
+cd $ISSMROOT
+module purge
+module load matlab
+module load intel/19.0.5
+module load mvapich2/2.3.2
+source $PBS_O_WORKDIR/../../etc/environment.sh
+
+matlab -nodesktop -nosplash -r "NAMEOFSCRIPT; exit"[[BR]]
+------
+
+4. If you are modifying source code and have previously built ISSM locally successfully, you should only need to run batch 6 which simply compiles the source code (and doesn't recompile all the dependencies).