GEOS-5

Setting up S2Sv3 model: Difference between revisions

← Older edit
 
(2 intermediate revisions by 2 users not shown)
Line 10: Line 10:
     cvs co -P -r tag_name GEOSodas_m7
     cvs co -P -r tag_name GEOSodas_m7
      
      
where <code>tag_name</code> is the name of the CVS tag of interest. It can be for instance <code>yuri-s2s3-unstable-SLES12</code>.
where <code>tag_name</code> is the name of the CVS tag of interest. Current S2Sv3 tag is <code>yuri-s2s3-unstable-FullModel</code>.


You will get a directory named <code>GEOSodas</code>.
You will get a directory named <code>GEOSodas</code>.
Line 24: Line 24:
In the last command, you might be asked to provide a <code>sponsor code id</code> is if you have more than one on the platform you are using.
In the last command, you might be asked to provide a <code>sponsor code id</code> is if you have more than one on the platform you are using.


An alternative method to compile the code is use a simple script (C-shell here) for a serial build. It assumes that that the script is located at the same level as the <code>GEOSodas/</code> directory.


    #!/bin/csh -f
     
    source /usr/share/modules/init/csh
     
    set curDIR = `pwd`
    setenv ESMADIR ${curDIR}/GEOSodas
     
    cd $ESMADIR/src
    module purge
    source g5_modules
     
    set CLEAN = 0
    set MAKEALL = 1
    set MAKEALLDEBUG = 0
     
    if ($CLEAN) gmake realclean
    if ($MAKEALLDEBUG) gmake install BOPT=g
    if ($MAKEALL) gmake pinstall


Regardless the method that you use to build the code, a directory named <code>Linux/</code> will be created inside <code>GEOSodas/</code>. The <code>Linux/</code> directory contains temporary files, libraries and executables created during the compilation process. To make sure that the code was successfully compiled, check that the file <code>GEOSgcm.x</code> exists in the directory <code>GEOSodas/src/Applications/GEOSgcm_App/</code>.
A directory named <code>Linux/</code> will be created inside <code>GEOSodas/</code>. The <code>Linux/</code> directory contains temporary files, libraries and executables created during the compilation process. To make sure that the code was successfully compiled, check that the file <code>GEOSgcm.x</code> exists in the directory <code>GEOSodas/src/Applications/GEOSgcm_App/</code>.
 
'''Note:''' To compile the model on Rome nodes at NAS, use <code>g5_modules_4ROME</code> modules file:
 
    cp g5_modules_4ROME g5_modules
    ./parallel_buid.csh
 
'''Note:''' To compile the model on Milan nodes at NCCS, use <code>yuri-s2s3-unstable-milan</code> tag and run the <code>parallel_build.csh</code> from Milan nodes:
   
    ssh discover-mil
    ...
    ./parallel_build.csh
 
or request an interactive SLURM session with <code>--constraint=mil</code> option and follow steps described above.


=== Create the Experiment Directory ===
=== Create the Experiment Directory ===
Line 66: Line 60:


* You want to run the COUPLED Ocean/Sea-Ice Model, answer <code>YES</code>.
* You want to run the COUPLED Ocean/Sea-Ice Model, answer <code>YES</code>.
* You want to to run the REPLAY DUAL OCEAN Model, answer
* You want to to run the REPLAY DUAL OCEAN Model,
** <code>YES</code> is you intend to run <code>ODAS</code>.
** Answer <code>YES</code> if you want to have the option of running <code>ODAS</code>.
** <code>NO</code> otherwise.
 


The available resolutions are:
The available resolutions are:
Retrieved from "https://geos5.org/wiki/index.php?title=Setting_up_S2Sv3_model"