Fortuna 2.4 Quick Start: Difference between revisions

(One intermediate revision by the same user not shown)

Line 1:

This page describes the minimum steps required to build and run GEOS-5 Fortuna 2.4 on NCCS discover and NAS pleiades. You should successfully complete the steps in these instructions before doing anything more complicated.

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

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

== How to Obtain GEOS-5 and Compile Source Code ==

Line 86:

The <code>umask 022</code> is not strictly necessary, but it will make the various files readable to others, which will facilitate data sharing and user support. Your home directory <code>~''USERID''</code> is also inaccessible to others by default; running <code>chmod 755 ~</code> is helpful.

Copy the restart (initial condition) files and associated <code>cap_restart</code> into ''EXPDIR''. Keep the "originals" handy since if the job stumbles early in the run it might stop after having renamed them. The model expects restart filenames to end in "rst" but produces them with the date and time appended, so you may have to rename them. The <code>cap_restart</code> file is simply one line of text with the date of the restart files in the format YYYYMMDD<space>HHMMSS. The boundary conditions/forcings are provided by symbolic links created by the run script.

Copy the restart (initial condition) files and associated <code>cap_restart</code> into ''EXPDIR''. Keep the "originals" handy since if the job stumbles early in the run it might stop after having renamed them. The model expects restart filenames to end in "rst" but produces them with the date and time appended, so you may have to rename them. The <code>cap_restart</code> file is often provided with a set of restarts, but if not you can create it: is simply one line of text with the date of the restart files in the format ''YYYYMMDD''<space>''HHMMSS''. The boundary conditions/forcings are provided by symbolic links created by the run script.

If you need an arbitrary set of restarts, you can copy them from <code>/archive/u/aeichman/restarts/Fortuna-2_4/</code>, where they are indexed by date and resolution.

Line 111:

The contents of the output files (including which variables get saved) may be configured in the <code>''HOMEDIR''/HISTORY.rc</code> -- a good description of this file may be found at http://modelingguru.nasa.gov/clearspace/docs/DOC-1190 .

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

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

@@ Line 1: / Line 1: @@
 This page describes the minimum steps required to build and run GEOS-5 Fortuna 2.4 on NCCS discover and NAS pleiades.  You should successfully complete the steps in these instructions before doing anything more complicated.
-Back to [[GEOS-5 Documentation for Fortuna 2.4]]
+'''Back to [[GEOS-5 Documentation for Fortuna 2.4]]'''
 == How to Obtain GEOS-5 and Compile Source Code ==
@@ Line 86: / Line 86: @@
 The <code>umask 022</code> is not strictly necessary, but it will make the various files readable to others, which will facilitate data sharing and user support.  Your home directory <code>~''USERID''</code> is also inaccessible to others by default; running <code>chmod 755 ~</code> is helpful.
-Copy the restart (initial condition) files and associated <code>cap_restart</code> into ''EXPDIR''.   Keep the "originals" handy since if the job stumbles early in the run it might stop after having renamed them.  The model expects restart filenames to end in "rst" but produces them with the date and time appended, so you may have to rename them.   The <code>cap_restart</code> file is simply one line of text with the date of the restart files in the format YYYYMMDD<space>HHMMSS.  The boundary conditions/forcings are provided by symbolic links created by the run script.
+Copy the restart (initial condition) files and associated <code>cap_restart</code> into ''EXPDIR''.   Keep the "originals" handy since if the job stumbles early in the run it might stop after having renamed them.  The model expects restart filenames to end in "rst" but produces them with the date and time appended, so you may have to rename them.   The <code>cap_restart</code> file is often provided with a set of restarts, but if not you can create it: is simply one line of text with the date of the restart files in the format ''YYYYMMDD''<space>''HHMMSS''.  The boundary conditions/forcings are provided by symbolic links created by the run script.
 If you need an arbitrary set of restarts, you can copy them from <code>/archive/u/aeichman/restarts/Fortuna-2_4/</code>, where they are indexed by date and resolution.
@@ Line 111: / Line 111: @@
 The contents of the output files (including which variables get saved) may be configured in the  <code>''HOMEDIR''/HISTORY.rc</code> -- a good description of this file may be found at http://modelingguru.nasa.gov/clearspace/docs/DOC-1190 .
-Back to [[GEOS-5 Documentation for Fortuna 2.4]]
+'''Back to [[GEOS-5 Documentation for Fortuna 2.4]]'''