Heracles Single Column Model: Difference between revisions

Setting Up and Running Existing SCM Experiments: Make "how to run" a bit more useful.
 
Line 70: Line 70:
Once the allocation is granted, it starts an interactive shell on the job node, from which you can run the GEOS-5 executable.  Since all of the necessary configuration files are copied to the experiment directory by <code>scm_setup</code>, running the SCM requires none of the extra environmental infrastructure needed for a global experiment that the run script <code>gcm_run.j</code> creates.
Once the allocation is granted, it starts an interactive shell on the job node, from which you can run the GEOS-5 executable.  Since all of the necessary configuration files are copied to the experiment directory by <code>scm_setup</code>, running the SCM requires none of the extra environmental infrastructure needed for a global experiment that the run script <code>gcm_run.j</code> creates.


To run the SCM, then issue:
To run the SCM, first, you'll need to source g5_modules and then you can run it:


  <nowiki>$ mpirun -np 1 ./GEOSgcm.x |& tee run.log
  <nowiki>$ setenv ESMADIR /discover/path/to/your/Heracles-5_2/GEOSagcm
$ source $ESMADIR/src/g5_modules
$ mpirun -np 1 ./GEOSgcm.x |& tee run.log
srun.slurm: cluster configuration lacks support for cpu binding
srun.slurm: cluster configuration lacks support for cpu binding