Fortuna 2.5 Quick Start: Difference between revisions
No edit summary |
|||
| (7 intermediate revisions by the same user not shown) | |||
| Line 22: | Line 22: | ||
where ''USERID'' is, of course, your repository username, which should be the same as your NASA and NCCS username. Then, issue the command: | where ''USERID'' is, of course, your repository username, which should be the same as your NASA and NCCS username. Then, issue the command: | ||
cvs co -r Fortuna- | cvs co -r Fortuna-2_5_p5 Fortuna | ||
This should check out the latest stable version of the model from the repository and create a directory called <code>GEOSagcm</code>. | This should check out the latest stable version of the model from the repository and create a directory called <code>GEOSagcm</code>. | ||
=== Compiling the Model === | === Compiling the Model === | ||
| Line 38: | Line 38: | ||
you should see: | you should see: | ||
Currently Loaded Modulefiles: | Currently Loaded Modulefiles: | ||
1) comp/intel-11.0.083 3) lib/mkl-10.0.3.020 5) other/SIVO-PyD/spd_1.0.0 | |||
2) mpi/impi-3.2.2.006 4) other/comp/gcc-4.5 | |||
If this all worked, then type: | If this all worked, then type: | ||
| Line 87: | Line 87: | ||
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. | 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 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 | 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 back to ending in "rst". 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 ''<code>YYYYMMDD HHMMSS</code>'' (with a space). 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- | If you need an arbitrary set of restarts, you can copy them from <code>/archive/u/aeichman/restarts/Fortuna-2_5/</code>, where they are indexed by date and resolution. | ||
| Line 98: | Line 98: | ||
== Output and Plots == | == Output and Plots == | ||
During a normal run, the <code>gcm_run.j</code> script will run the model for the segment length (current default is | During a normal run, the <code>gcm_run.j</code> script will run the model for the segment length (current default is 10 days). The model creates output files (with an <code>nc4</code> extension), also called collections (of output variables), in <code>''EXPDIR''/scratch</code> directory. After each segment, the script moves the output to the <code>''EXPDIR''/holding</code> and spawns a post-processing batch job which partitions and moves the output files within the <code>holding</code> directory to their own distinct collection directory, which is again partitioned into the appropriate year and month. The post processing script then checks to | ||
see if a full month of data is present. If not, the post-processing job ends. If there is a full month, the script will then run the time-averaging executable to produce a monthly mean file in <code>''EXPDIR''/ | see if a full month of data is present. If not, the post-processing job ends. If there is a full month, the script will then run the time-averaging executable to produce a monthly mean file in <code>''EXPDIR''/geosgcm_*</code>. The post-processing script then spawns a new batch job which will archive the data onto the mass-storage drives (<code>/archive/u/''USERID''/GEOS5.0/''EXPID''</code>). | ||
If a monthly average file was made, the post-processing script will also | If a monthly average file was made, the post-processing script will also | ||
| Line 112: | Line 112: | ||
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 . | 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. | '''Back to [[GEOS-5 Documentation for Fortuna 2.5]]''' | ||