Changes between Version 7 and Version 8 of Projects/OpenIFS-IO

Timestamp:

23/09/13 17:13:50 (6 years ago)

Author:

grenville

Comment:

—

Projects/OpenIFS-IO

@@ -81 +81 @@
 }}}
 
-This cumbersome command can be made simpler by use of FCM keywords and of course you can use aliasing to reduce the amount of typing required. However, it is instructive to see the command in its entirety (actually we have already defined the keyword oifs to save some typing). The text after fcm co is the URL for the code which exposes some of the structure of the underlying code repository. In this case the code is in a '''branch''' owned by '''dev'''eloper '''grenville'''; the branch is called '''38r1v02_fdb_updates''' and the code is at ('''@''') revision number '''16'''. This is just standard FCM (svn) terminology.
+This cumbersome command can be made simpler by use of FCM keywords and of course you can use aliasing to reduce the amount of typing required. However, it is instructive to see the command in its entirety (actually we have already defined the keyword oifs to save some typing). The text after fcm co is the URL for the code which exposes some of the structure of the underlying code repository. In this case the code is in the '''branches''' section of the repository  owned by '''dev'''eloper '''grenville'''; the branch is called '''38r1v02_fdb_updates''' and the code is at ('''@''') revision number '''16'''. This is just standard FCM (svn) terminology.
 
 This is the simplest way to get OIFS code - it will often be the case that you wish to extract from several branches and possibly a working copy - see later.
+
+=== Build the OIFS executable ===
 
 After executing this command on HECToR, you will have a complete copy of the code in your /home space. A set of configuration files is provided in the oifs/make sub-directory for several possible compilers and options. When you loaded the openifs_cce/0.0.2 module, you set several environment variables which determine the particular configuration files to choose. In the make directory type
@@ -91 +93 @@
 }}}
 
-which runs the compile and link phases of the build, using 4 processors (-j 4), with verbose output (-vv) based on the configuration file in cfg/oifs.cfg (the -f option) (see the FCM documentation for more options for the fcm make command).
+this runs the compile and link phases of the build, using 4 processors (-j 4), with verbose output (-vv) based on the configuration file in cfg/oifs.cfg (the argument of -f option) (see the FCM documentation for more options for the fcm make command). This may take some time.
+
+The executable, currently called master.exe, will be in make/opt/oifs/bin.
+
+=== Getting data to run the model ===
+
+The source for data is Glenn Carver at ECMWF. Glenn can provide start data for configurations at several resolutions and for various times. We have several jobs available for model testing at t159, t511 and t1279 resolution. Each job comes with data required to start the model, a namelist with a set of model parameters, a PBS script set up for a "standard" run and an example trace output file. We will give a description of the PBS script used to submit jobs to the computer nodes.
+
+{{{
+#!/bin/bash --login
+#
+#       Jobname
+#PBS -N openifs
+#       Total no. of tasks (MPIxOpenMP) for job
+#PBS -l mppwidth=1024
+#       No. of tasks per node (1-32)
+#PBS -l mppnppn=32
+#       Time for the job
+#PBS -l walltime=00:25:00
+#       Account
+#PBS -A n02-cms
+#       Squash output & error output together
+#PBS -j oe
+#       Mail options
+#PBS -M g.m.s.lister@reading.ac.uk
+#PBS -m ae
+
+
+# Set environment
+source $HOME/oifs.setup
+
+set -x
+
+# Make sure any symbolic links are resolved to absolute path
+export PBS_O_WORKDIR=$(readlink -f $PBS_O_WORKDIR)
+
+# Chnage to the directory the job was submitted from
+cd $PBS_O_WORKDIR
+
+#  Root directory of OpenIFS
+#export OIFS_HOME=$HOME/oifs38r1v01
+#  make sure correct branch is active
+#export OIFS_HOME=$HOME/git/openifs
+export OIFS_HOME=$HOME/oifs_extract/extract/oifs
+
+#  Set the GRIB_SAMPLES_PATH to your installation
+#  set DEFINITION_PATH so grib_api can find boot.def 
+#  set OIFS_GRIB_API_DIR to point to local installation
+export GRIB_SAMPLES_PATH=$GRIB_API_PATH/share/grib_api/ifs_samples/grib1_mlgrib2
+export GRIB_DEFINITION_PATH=$GRIB_API_PATH/share/grib_api/definitions
+
+#  use assign statement to read f77 unformatted files as big-endian
+#  as model was not compiled with -h byteswapio
+export FILENV=$PBS_O_WORKDIR/.myassign
+assign -N swap_endian g:su
+
+# Run model
+EXPID=fw13
+NPROC=128
+NTHREADS=8
+RUN=6
+TSTEP=600
+MASTER=$OIFS_HOME/make/opt/oifs/bin/master.exe
+NAMELIST=ecmwf/$EXPID.namelistfc
+
+/work/n02/n02/emgdc/oifs/ifs_run.sh -m $MASTER -r 511 -e $EXPID -s $TSTEP -n $NPROC \
+                                    -t $NTHREADS -f d1 -x $RUN -l $NAMELIST
+
+exit 0
+}}}