Fortuna 2.5 Single Column Model: Difference between revisions

Line 1:

This page describes the steps and modifications necessary to build and run the Single Column Model (SCM) under Fortuna 2.4 on discover. It assumes that you have successfully run the model as described in [[Fortuna 2.4 Quick Start]].

This page describes the steps and modifications necessary to build and run the Single Column Model (SCM) under Fortuna 2.5 on discover. It assumes that you have successfully run the model as described in [[Fortuna 2.5 Quick Start]].

'''Back to [[GEOS-5 Documentation for Fortuna 2.4]]'''

'''Back to [[GEOS-5 Documentation for Fortuna 2.5]]'''

== Checking Out and Updating GEOS-5 for SCM ==

The Fortuna model tag <code>Fortuna-~~2_4~~</code> has all code necessary to run the single column model with any of the cases below.

The Fortuna model tag <code>Fortuna-2_5</code> has all code necessary to run the single column model with any of the cases below. '''The executable of the Single Column Model is identical to the global model'''; the only differences are the environment and settings with which it runs.

== Setting Up and Running Existing SCM Experiments ==

Line 27:

Create your own directory and copy to it the script <code>getSCMdataf2.4.sh</code>, then modify and uncomment the first executable line, which assigns <code>ESMADIR</code> to your local Fortuna 2.2 build that you are using for the SCM (you may already have this set as an environment variable). Uncomment one of the lines that assign the variable <code>CASEDIR</code> to choose the experiment to run. Then run the script. It will copy all of the necessary resource, forcing and data files to the working directory. Each experiment requires its own directory. If you modify the resource files (e.g., HISTORY.rc) you may want to copy the setup directory to your own area and modify it and the setup script accordingly so that you don't clobber your modifications.

Create your own directory and copy to it the script <code>getSCMdataf2.5.sh</code>, then modify and uncomment the first executable line, which assigns <code>ESMADIR</code> to your local Fortuna 2.5 build that you are using for the SCM (you may already have this set as an environment variable). Uncomment one of the lines that assign the variable <code>CASEDIR</code> to choose the experiment to run. Then run the script. It will copy all of the necessary resource, forcing and data files to the working directory. Each experiment requires its own directory. If you modify the resource files (e.g., HISTORY.rc) you may want to copy the setup directory to your own area and modify it and the setup script accordingly so that you don't clobber your modifications.

Then you can just run the model executable from the command line in the directory you created. You will have to load the proper modules by sourcing <code>src/g5_modules</code>. Although it runs with a single processor, on discover you should run it from an interactive job on a compute node (as opposed to the '''discover''' front end). This can be done by running <code>qsub -I ijob</code>, where <code>ijob</code> is the job script that sets up the environment (examples are in <code>~aeichman</code> or <code>~amolod</code>). Once the job starts 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, it requires none of the extra environmental infrastructure needed for a global experiment that the run script <code>gcm_run.j</code> creates.

@@ Line 1: / Line 1: @@
-This page describes the steps and modifications necessary to build and run the Single Column Model (SCM) under Fortuna 2.4 on discover.  It assumes that you have successfully run the model as described in [[Fortuna 2.4 Quick Start]].
+This page describes the steps and modifications necessary to build and run the Single Column Model (SCM) under Fortuna 2.5 on discover.  It assumes that you have successfully run the model as described in [[Fortuna 2.5 Quick Start]].
-'''Back to [[GEOS-5 Documentation for Fortuna 2.4]]'''
+'''Back to [[GEOS-5 Documentation for Fortuna 2.5]]'''
 == Checking Out and Updating GEOS-5 for SCM ==
-The Fortuna model tag <code>Fortuna-2_4</code> has all code necessary to run the single column model with any of the cases below.
+The Fortuna model tag <code>Fortuna-2_5</code> has all code necessary to run the single column model with any of the cases below.  '''The executable of the Single Column Model is identical to the global model'''; the only differences are the environment and settings with which it runs.
 == Setting Up and Running Existing SCM Experiments ==
@@ Line 27: / Line 27: @@
-Create your own directory and copy to it the script <code>getSCMdataf2.4.sh</code>, then modify and uncomment the first executable line, which assigns <code>ESMADIR</code> to your local Fortuna 2.2 build that you are using for the SCM (you may already have this set as an environment variable).  Uncomment one of the lines that assign the variable <code>CASEDIR</code> to choose the experiment to run.  Then run the script.  It will copy all of the necessary resource, forcing and data files to the working directory.  Each experiment requires its own directory.  If you modify the resource files (e.g., HISTORY.rc) you may want to copy the setup directory to your own area and modify it and the setup script accordingly so that you don't clobber your modifications.
+Create your own directory and copy to it the script <code>getSCMdataf2.5.sh</code>, then modify and uncomment the first executable line, which assigns <code>ESMADIR</code> to your local Fortuna 2.5 build that you are using for the SCM (you may already have this set as an environment variable).  Uncomment one of the lines that assign the variable <code>CASEDIR</code> to choose the experiment to run.  Then run the script.  It will copy all of the necessary resource, forcing and data files to the working directory.  Each experiment requires its own directory.  If you modify the resource files (e.g., HISTORY.rc) you may want to copy the setup directory to your own area and modify it and the setup script accordingly so that you don't clobber your modifications.
 Then you can just run the model executable from the command line in the directory you created.  You will have to load the proper modules by sourcing <code>src/g5_modules</code>.  Although it runs with a single processor, on discover you should run it from an interactive job on a compute node (as opposed to the '''discover''' front end).  This can be done by running <code>qsub -I ijob</code>, where <code>ijob</code> is the job script that sets up the environment (examples are in <code>~aeichman</code> or <code>~amolod</code>).  Once the job starts 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, it requires none of the extra environmental infrastructure needed for a global experiment that the run script <code>gcm_run.j</code> creates.