Ganymed 4.0 Quick Start: Difference between revisions
Created page with "This page describes the minimum steps required to build and run GEOS-5 Ganymed 3.0 on NCCS discover and NAS pleiades. '''You should successfully complete the steps in these inst..." |
No edit summary |
||
Line 1: | Line 1: | ||
This page describes the minimum steps required to build and run GEOS-5 Ganymed | This page describes the minimum steps required to build and run GEOS-5 Ganymed 4.0 on NCCS discover and NAS pleiades. '''You should successfully complete the steps in these instructions before doing anything more complicated. Also, it is helpful to read this page in its entirety before starting.''' | ||
'''Back to [[GEOS-5 Documentation for Ganymed | '''Back to [[GEOS-5 Documentation for Ganymed 4.0]]''' | ||
== How to Obtain GEOS-5 and Compile Source Code == | == How to Obtain GEOS-5 and Compile Source Code == | ||
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 Ganymed- | cvs co -r Ganymed-4_0_BETA1 Ganymed | ||
This should check out the latest stable version of the model from the repository and create a directory called <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 === | ||
<code>cd</code> into <code> | <code>cd</code> into <code>GEOSagcm/src</code> and <code>source</code> the file called <code>g5_modules</code>: | ||
source g5_modules | source g5_modules | ||
Line 40: | Line 40: | ||
Currently Loaded Modulefiles: | Currently Loaded Modulefiles: | ||
1) comp/intel- | 1) comp/intel-13.1.2.183 4) other/comp/gcc-4.6.3-sp1 | ||
2) other/mpi/mvapich2-1.8.1/intel- | 2) other/mpi/mvapich2-1.8.1/intel-13.1.2.183 5) other/SIVO-PyD/spd_1.10.0_gcc-4.6.3-sp1 | ||
3) lib/mkl-13.0.1.117 | |||
If this all worked, then type: | If this all worked, then type: | ||
Line 47: | Line 49: | ||
gmake install | gmake install | ||
This will build the model. It will take about | This will build the model. It will take about 30 minutes. If this works, it should create a directory under <code>GEOSagcm</code> called <code>Linux/bin</code>. In here you should find the executable: <code>GEOSgcm.x</code> . | ||
== Setting up a Run == | == Setting up a Run == | ||
Line 63: | Line 65: | ||
Then, log into '''dirac''' and cut and paste the contents of the <code>id_rsa.pub</code> and <code>id_dsa.pub</code> files on '''discover''' into the <code>~/.ssh/authorized_keys</code> file on '''dirac'''. Problems with <code>ssh</code> should be referred to NCCS support. | Then, log into '''dirac''' and cut and paste the contents of the <code>id_rsa.pub</code> and <code>id_dsa.pub</code> files on '''discover''' into the <code>~/.ssh/authorized_keys</code> file on '''dirac'''. Problems with <code>ssh</code> should be referred to NCCS support. | ||
To set the model up to run, cd to <code> | To set the model up to run, cd to <code>GEOSagcm/src/Applications/GEOSgcm_App</code> and run: | ||
./gcm_setup | ./gcm_setup | ||
Line 91: | Line 93: | ||
Do you wish to run the COUPLED Ocean/Sea-Ice Model? (Default: NO or FALSE) | Do you wish to run the COUPLED Ocean/Sea-Ice Model? (Default: NO or FALSE) | ||
Enter the Data_Ocean Horizontal Resolution code: o1 (1 -deg, | Enter the Data_Ocean Horizontal Resolution code: o1 (1 -deg, 360x180 Reynolds) Default | ||
o2 (1/4-deg, 1440x720 MERRA-2) | |||
o3 (1/8-deg, 2880x1440 OSTIA) | |||
Do you wish to run GOCART? (Default: NO or FALSE) | Do you wish to run GOCART? (Default: NO or FALSE) | ||
Line 153: | Line 157: | ||
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''. You can get an arbitrary set of restarts by copying the contents of the directory <code>/archive/u/aeichman/restarts/Ganymed- | Copy the restart (initial condition) files and associated <code>cap_restart</code> into ''EXPDIR''. You can get an arbitrary set of restarts by copying the contents of the directory <code>/archive/u/aeichman/restarts/Ganymed-4_0/C48/19800103/</code>, containing 2-degree cubed sphere restarts from Jan. 3, 1980, and their corresponding <code>cap_restart</code>. If you are unfamiliar with the way that the <code>/archive</code> filesystem works, keep in mind that a <code>cp</code> from there might appear to stall while the tape is loaded -- see the NCCS documentation for details. | ||
The script you submit, <code>gcm_run.j</code>, is in ''HOMEDIR''. It should be ready to go as is. The parameter END_DATE in <code>CAP.rc</code> can be set to the date you want the run to stop. An alternative way to stop the run is by commenting out the line <code> if ( $capdate < $enddate ) qsub $HOMDIR/gcm_run.j</code> at the end of the script, which will prevent the script from being resubmitted, or rename the script file, or kill the job (described below). | The script you submit, <code>gcm_run.j</code>, is in ''HOMEDIR''. It should be ready to go as is. The parameter END_DATE in <code>CAP.rc</code> can be set to the date you want the run to stop. An alternative way to stop the run is by commenting out the line <code> if ( $capdate < $enddate ) qsub $HOMDIR/gcm_run.j</code> at the end of the script, which will prevent the script from being resubmitted, or rename the script file, or kill the job (described below). |