Difference between revisions of "OpenIFS"
Line 1: | Line 1: | ||
− | === OpenIFS - Open Integrated Forecasting System | + | === OpenIFS - Open Integrated Forecasting System === |
OpenIFS provides academic and research institutions with an easy-to-use version of the ECMWF IFS (Integrated Forecasting System). OpenIFS provides the forecast capability of IFS (no data assimilation), supporting software and documentation. OpenIFS has a support team at ECMWF for technical assistance but limited resources for detailed scientific assistance. | OpenIFS provides academic and research institutions with an easy-to-use version of the ECMWF IFS (Integrated Forecasting System). OpenIFS provides the forecast capability of IFS (no data assimilation), supporting software and documentation. OpenIFS has a support team at ECMWF for technical assistance but limited resources for detailed scientific assistance. | ||
[https://software.ecmwf.int/wiki/display/OIFS/About+OpenIFS About OpenIFS] provides more information about the model. | [https://software.ecmwf.int/wiki/display/OIFS/About+OpenIFS About OpenIFS] provides more information about the model. | ||
− | |||
− | |||
− | |||
− | |||
Line 40: | Line 36: | ||
− | For building openIFS, we use | + | For building openIFS, we use intel compilers: |
<pre>module list | <pre>module list | ||
Currently Loaded Modulefiles: | Currently Loaded Modulefiles: | ||
Line 49: | Line 45: | ||
== Running openIFS: == | == Running openIFS: == | ||
+ | |||
+ | The main openIFS program (forecast model) is called master.exe but as for most models, several steps have to be done before the first call to master.exe! | ||
+ | |||
+ | The main steps are: | ||
+ | |||
+ | - get meteorological input fields (see examples on how to get ECMWF reanalysis data with ecmwfapi). | ||
+ | |||
+ | - interpolate input fields to the chosen horizontal and vertical resolution | ||
+ | |||
+ | - run forecast model to generate output fields | ||
+ | |||
+ | |||
+ | |||
+ | To perform these steps, some python scripts have been developed: | ||
+ | |||
+ | ==== Step-1: get meteorological input fields ==== | ||
+ | |||
+ | *getEIdata.py | ||
+ | |||
+ | ==== Step-2: interpolate input fields to the chosen horizontal and vertical resolution ==== | ||
+ | |||
+ | *prepareInterpolationEIdata.py | ||
+ | *runInterpolation.py | ||
+ | *postInterpolationEIdata.py | ||
+ | |||
+ | ==== Step-3: run oenIFS forecast model ==== | ||
+ | |||
+ | *prepareOpenifsRun.py | ||
+ | *runOpenIFS.py | ||
+ | |||
+ | |||
+ | |||
+ | <u>TIPS</u>: to get the usage of these python scripts, use -h or --help. For instance: | ||
+ | |||
+ | getEIdata.py -h<br/>Usage: getEIdata.py --start_date=YYYYMMDD [--end_date=YYYYMMDD] [--times=tt1/tt2/tt3]<br/> [--grid_type=gtype] [--levels=nlevels]<br/> [--sfc=sfc.grb] [--ggml=ggml.grb] [--shml=shml.grb]<br/> [--inputdir=input_directory] [--outputdir=output_directory]<br/><br/>Options:<br/> -h, --help show this help message and exit<br/> -s start_date, --start_date=start_date<br/> start date YYYYMMDD<br/> -e end_date, --end_date=end_date<br/> end_date YYYYMMDD<br/> -t times, --times=times<br/> times such as 00/12<br/> -l levels, --levels=levels<br/> number of levels i.e. 60<br/> --sfc=sfc output filename where surface data will be stored<br/> --ggml=ggml output filename where upper data on reduced gaussion<br/> grid will be stored<br/> --shml=shml output filename where shperical harmonic upper data<br/> will be stored<br/> --inputdir=inputdir root directory for reading input files (valid when<br/> retrieve=no)<br/> --outputdir=outputdir<br/> root directory for storing output files<br/> --grid_type=grid_type<br/> grid type default is l_2<br/><br/> | ||
+ | |||
+ | <span style="color:#ff0000">'''For each of these python scripts, some arguments are optionals and indicated in squared brackets such as end_date.'''</span> | ||
+ | |||
+ | <span style="color:#ff0000"</span> | ||
+ | |||
+ | |||
== openIFS examples: == | == openIFS examples: == |
Revision as of 10:02, 2 December 2014
OpenIFS - Open Integrated Forecasting System
OpenIFS provides academic and research institutions with an easy-to-use version of the ECMWF IFS (Integrated Forecasting System). OpenIFS provides the forecast capability of IFS (no data assimilation), supporting software and documentation. OpenIFS has a support team at ECMWF for technical assistance but limited resources for detailed scientific assistance.
About OpenIFS provides more information about the model.
First check openifs availability on your platform. Currently openIFS is available on UIO HPC (abel.uio.no) only.
module avail openifs -------------------------------------------------------------------------------- /cluster/etc/modulefiles --------------------------------------------------------------------------------- openifs/38r1v04(default)
If nothing is returned, it is likely openifs is not available. If you think it should, then contact us (drift@uio.no).
To load a given openifs version:
module load openifs/38r1v04
We suggest you specify the version you wish to use to avoid any problems if we install a new default version (as it is important to stick to the very same version for your simulations).
When loading openifs the following environment variables are defined:
- OIFS_CYCLE: ECMWF cycle such as 38r1 (version 38, revision 1)
- OIFS_HOME: directory where openIFS has been installed; this can be used to check openIFS sources
- OIFS_DATA: contains openIFS static input data. Even if you use your own compiled version of openIFS, it is NOT necessary to download these files again.
- OIFS_EXAMPLES: directory where all openIFS examples are stored. If you wish to run one of these examples see our dedicated section on running tutorials.
- OIFS_COMP: compilers used to create openIFS executables. We currently use intel compilers.
- OIFS_BUILD: type of build. It triggers a set of compiler options when building openIFS. Currently set to "opt"
- OIFS_GRIB_API_DIR: GRIB-API version used by openIFS to encode/decode GRIB files
- MARS_LSM_PATH: land sea mask used
- EMOS_VERSION: EMOS version (compiled with GRIB-API support). EMOS is used for interpolation routines.
- EMOS_HOME: directory where EMOS has been installed.
- BUFR_TABLES: bufrtables used for decoding/encoding BUFR (not used in the forecast model)
- CREX_TABLES: crex tables used for encoding/decoding CREX data.
For building openIFS, we use intel compilers:
module list Currently Loaded Modulefiles: 1) use.own 3) openmpi.intel/1.6.1 5) hdf5/1.8.9_intel 7) grib_api/1.12.3 9) udunits/2.2.16 11) intelmpi.intel/4.1.3 2) intel/2011.10 4) python2/2.7.3 6) netcdf.intel/4.2.1.1 8) perlmodules/5.10_2 10) intel/2013.sp1.1 12) openifs/38r1v04
Running openIFS:
The main openIFS program (forecast model) is called master.exe but as for most models, several steps have to be done before the first call to master.exe!
The main steps are:
- get meteorological input fields (see examples on how to get ECMWF reanalysis data with ecmwfapi).
- interpolate input fields to the chosen horizontal and vertical resolution
- run forecast model to generate output fields
To perform these steps, some python scripts have been developed:
Step-1: get meteorological input fields
- getEIdata.py
Step-2: interpolate input fields to the chosen horizontal and vertical resolution
- prepareInterpolationEIdata.py
- runInterpolation.py
- postInterpolationEIdata.py
Step-3: run oenIFS forecast model
- prepareOpenifsRun.py
- runOpenIFS.py
TIPS: to get the usage of these python scripts, use -h or --help. For instance:
getEIdata.py -h
Usage: getEIdata.py --start_date=YYYYMMDD [--end_date=YYYYMMDD] [--times=tt1/tt2/tt3]
[--grid_type=gtype] [--levels=nlevels]
[--sfc=sfc.grb] [--ggml=ggml.grb] [--shml=shml.grb]
[--inputdir=input_directory] [--outputdir=output_directory]
Options:
-h, --help show this help message and exit
-s start_date, --start_date=start_date
start date YYYYMMDD
-e end_date, --end_date=end_date
end_date YYYYMMDD
-t times, --times=times
times such as 00/12
-l levels, --levels=levels
number of levels i.e. 60
--sfc=sfc output filename where surface data will be stored
--ggml=ggml output filename where upper data on reduced gaussion
grid will be stored
--shml=shml output filename where shperical harmonic upper data
will be stored
--inputdir=inputdir root directory for reading input files (valid when
retrieve=no)
--outputdir=outputdir
root directory for storing output files
--grid_type=grid_type
grid type default is l_2
For each of these python scripts, some arguments are optionals and indicated in squared brackets such as end_date.
<span style="color:#ff0000"</span>
openIFS examples:
There are 3 examples currently available:
cd $OIFS_EXAMPLES ls ei osloctm t21test
T21 simple test:
Choose a directory of your choice and copy this simple test:
mkdir -p $HOME/openifs/examples cd $HOME/openifs/examples cp -R $OIFS_EXAMPLES/t21test . cd t21test ls fort.4 ICMGGepc8 ICMGGepc8INIT ICMGGepc8INIUA ICMSHepc8 ICMSHepc8INIT ifsdata job namelists README ref_021_0144 ./job_uio
This is a very short and simple example and it can be run interactively (./job_uio).
All the input fields are already available and by executing job_uio, you run ECMWF openIFS forecast model.
Output fields generated by openIFS are:
ICMSHepc8+000000 ICMGGepc8+000000
SH means Spherical harmonics and GG Gaussian grid. These files are in GRIB-2 format.
You may convert these GRIB files to netCDF using cdo; for instance on sverdrup:
module load cdo/1.6.5.1 cdo -t ecmwf -f nc copy ICMSHepc8+000000 ICMSHepc8+000000.nc
For more information, see ECMWF How to convert OpenIFS outputs to netCDF.