ecCodes<\/strong><\/li>\n<\/ul>\nConfigure AAPP<\/h3>\n
This section is split into 2 parts: firstly the instructions for configuring a “core” AAPP installation with no external libraries (which may be adequate for some users), and secondly the instructions for creating a fuller installation. Note that the procedure uses a perl script named configure<\/span> that is located in the AAPP top directory. (It does not use GNU autotools).<\/p>\nConfigure the “core” AAPP<\/h4>\n
All that is required to install “core” AAPP is to go to the AAPP top directory and run the configure<\/span> script with your site-id specified as:
\n\u2212\u2212site-id=\u00a0<\/span>a 3-character abbreviation of your centre
\nand the Fortran compiler you are using as
\n\u2212\u2212fortran-compiler=<\/span> any of : gfortran ifort pgf90 g95 AIX AIX-Hitachi
\nFor example, to configure AAPP for a Linux system using gfortran you could type (from the top directory)
\n<divstyle=”margin-left: 40px;=”” margin-top:=”” 10px;=”” height:=”” 15px;=””><spanchecked=”true”style=”font-family: courier=”” new,courier,monospace;=””>
\n.\/configure \u2212\u2212site-id=UKM \u2212\u2212fortran-compiler=gfortran<\/span>
\n<\/spanchecked=”true”style=”font-family:><\/divstyle=”margin-left:> There are additional options (type .\/configure<\/span> from the top directory to view them) that you may wish to specify, such as your local station name, and some must be specified to obtain full AAPP functionality as described below. But to complete the “core” AAPP installation type
\nmake<\/span><\/p>\nCheck that the installation was successful and that you did not see any errors. If it was OK you may start testing AAPP. You will be able to run the NOAA test case and parts of the Metop test case.<\/p>\n
Configure your “fuller” AAPP installation<\/h4>\n
Go to the AAPP top directory<\/span> and type .\/configure<\/span> to see the options.<\/p>\nYou have to specify the following:<\/p>\n
\u2212\u2212site-id=\u00a0 <\/span>a 3-character abbreviation of your centre
\n\u2212\u2212fortran-compiler=<\/span>any of : gfortran ifort pgf90 AIX AIX-Hitachi<\/div>\nNote 1: To see the complete list of compilers that have been used in past versions of AAPP, check the contents of the files in directory config<\/span>. However, some of these are no longer supportable by the NWP SAF due to their age and lack of test platforms. In particular, we no longer recommend the use of a FORTRAN77 compiler such as g77, as many parts of AAPP will not build. Also g95 does not work with the MAIA4 calls in avh2hirs.<\/p>\nNote 2: Some Fortran 90 compilers require different flags to indicate the directory to search for Module files. The default is “-I”, but you may need “-M”. If necessary, you can adjust the applicable file in the config<\/span> directory (and please inform the NWP SAF Helpdesk if you find something that needs changing).<\/p>\nIn addition, you can optionally specify:<\/p>\n
\u2212\u2212prefix=<\/span> installation prefix, if you wish to install the AAPP executables and data files to somewhere other than the current directory e.g. $HOME\/AAPP_8_runtime
\nNote: do not<\/em> choose this directory to be the same as the AAPP top directory, otherwise all your source files will be deleted!
\n\u2212\u2212station=<\/span> your local station name (see list in AAPP\/src\/navigation\/libnavtool\/stations.txt). The default is “dummy_station”
\n\u2212\u2212station-id=<\/span> your local station ID, for “datset name” field in the level 1a\/1b header. The default is WE (Western Europe)
\n\u2212\u2212external-libs=<\/span> location and options for external libraries (in quotes), e.g. “-L${DIR_ECCODES}\/lib -leccodes -leccodes_f90 -L${DIR_HDF5}\/lib -lhdf5 -lhdf5_hl -lhdf5_fortran -lhdf5hl_fortran”<\/span>.
\n\u2212\u2212external-includes=<\/span> location and library options for external include files, e.g. -I${DIR_HDF5}\/include<\/span>
\n\u2212\u2212external-modules=<\/span> location for external Fortran90 modules, e.g. -M ${DIR_ECCODES}\/include<\/span>
\nNote: some compilers use “-I”<\/span> instead of “-M”<\/span>.
\n\u2212\u2212c-compiler=<\/span> name of your C compiler (for use with METOP tools, IASI tools and HDF5).
\n\u2212\u2212tle-user=<\/span> www.space-track.org username; required for using tle retrieval from the internet.
\n\u2212\u2212tle-passwd=<\/span> www.space-track.org password
\n\u2212\u2212scriptdir=<\/span> optional directory in which to place the AAPP shell scripts. Normally the scripts and .exe files are placed together in “bin” directories, but on some systems, notably Cygwin, they must be separated, e.g. specify “scripts”.<\/div>\nIf an external library is centrally installed on your system (e.g. in \/usr\/lib), you will not need to specify -L<\/span> under \u2212\u2212external libs<\/span>, but you will need to link to it using -l<\/span>. Similarly, if your external library has centrally-installed include files (e.g. in \/usr\/include) then you will not need to specify \u2212\u2212external-includes<\/span>.<\/p>\nRegarding HDF5: if you do not need to run MAIA, and just want the HDF5 conversion tools, it is sufficient to just specify “-lhdf5<\/span>“. Some systems may require -lz<\/span>.<\/p>\nYou will probably need to use the same Fortran compiler for AAPP as was used to build the HDF5 Fortran interface. You may also need some of the same compiler flags (e.g. “-qextname” for the AIX xlf compiler).<\/p>\n
If the Fortran compiler you wish to use is not listed, you may create your own configuration file in the config<\/em> directory, taking one of the existing ones as a template. If you do so successfully, please inform the NWP SAF, for the benefit of other users.<\/p>\nIf your station is not contained in the station list file, AAPP\/src\/navigation\/libnavtool\/stations.txt<\/b>, you can edit and update the file if necessary before you go on to build AAPP. Please notify the NWP SAF of the coordinates of your station, so that it can be included in a future update.<\/p>\n
The “station”, “station_id”, “tle_user” and “tle_password” options are optional. The values that you enter are stored in the ATOVS_ENV8 file. You may edit this file later if you want to change the values.<\/p>\n
When you build AAPP, the source, data files and executables are initially placed in a fixed directory tree structure as follows:<\/p>\n
AAPP_8\/AAPP\/bin
\nAAPP_8.1\/AAPP\/data
\nAAPP_8.1\/AAPP\/src
\nAAPP_8.1\/metop-tools\/bin
\nAAPP_8.1\/metop-tools\/src
\netc.<\/span><\/div>\nThis will be fine for many users. However, if the “prefix” option is specified then you can install elsewhere the bin<\/em> and data<\/em> directories, and other files needed at run time. This is done via the “make install” command. The path that you enter is also stored in the ATOVS_ENV8 file, as environment variable AAPP_PREFIX. If you do not use the “prefix” option then AAPP_PREFIX is set to the AAPP top directory.<\/p>\nThus the run-time directories are always $AAPP_PREFIX\/AAPP\/bin<\/span>, $AAPP_PREFIX\/AAPP\/data<\/span>, etc.<\/p>\nFor example, an installation with hdf5, BUFRDC and ecCodes capability could be set up like this:<\/p>\n
hdf=\/path_to_hdf5\r\nbufr=\/path_to_bufrdc\r\nec=\/path_to_eccodes\r\n\r\n[[ ${LD_LIBRARY_PATH:-} = *${hdf}* ]] || export LD_LIBRARY_PATH=${LD_LIBRARY_PATH:+$LD_LIBRARY_PATH:}${hdf}\/lib\r\n[[ ${LD_LIBRARY_PATH:-} = *${ec}* ]] || export LD_LIBRARY_PATH=${LD_LIBRARY_PATH:+$LD_LIBRARY_PATH:}${ec}\/lib\r\nconfigure \u2212\u2212station=exeter \u2212\u2212fortran-compiler=ifort \u2212\u2212site-id=UKM \\\r\n \u2212\u2212external-libs=\"-L$bufr\/lib -lbufr -L$ec\/lib -leccodes -leccodes_f90 -L$hdf\/lib -lhdf5 -lhdf5_hl -lhdf5_fortran -lhdf5hl_fortran\" \\\r\n \u2212\u2212external-includes=\"-I$hdf\/include -I$ec\/include\"\r\n<\/pre>\nIf a library is centrally installed on your system you will not need to modify LD_LIBRARY_PATH<\/span>. The error messages from the build step should tell you if any libraries are missing.<\/p>\nThe configure<\/em> script creates a file <em”>Makefile.ARCH in the top directory, which contains the system settings and is referenced by all the lower-level makefiles. You may wish to modify the contents of this file before proceeding, for example:<\/p>\n\n- to change some of the compiler flags. In particular you are advised to check that the optimisation flags are suitable for your system.<\/li>\n
- to provide an explicit path to the Fortran compiler.<\/li>\n<\/ul>\n
Some components of AAPP may be customised by the user. For example, the IASI level 1d format is defined by the file AAPP\/include\/iasi1d.h<\/em>. This file has parameters that define the maximum number of Principal Components scores that can be accommodated in the 1d file, and the maximum number of channels. If you want something other than the default (500 channels, plus 300 scores) then you should modify this file before building the software. The number of channels or scores actually used<\/em> may be set at run time, provided it is less than the maximum.<\/p>\nBuild AAPP<\/h3>\n
To build the complete package you just need to do one of the following:<\/p>\n
If you did not specify an installation prefix in the
configure<\/span> step, type<\/div>\nmake<\/span><\/p>\nIf you did specify an installation prefix, type<\/div>\n
make install<\/span><\/div>\nThere are a number of other possibilities that users requiring flexibility may adopt:<\/p>\n
\n- AAPP v8 comprises three main components: (i) the core AAPP, (ii) METOP tools and (iii) IASI tools. To build or re-build just one component, cd<\/span> to the appropriate directory (AAPP, metop-tools or iasi-tools) then run make<\/em> as before. Note that metop-tools must be built before iasi-tools. However, it is advisable to first run make<\/em> from the top of the AAPP tree in order to avoid problems with library dependencies.<\/li>\n
- To clean the whole of AAPP, i.e. to delete all the binaries, libraries, data files and object files in the AAPP_8 tree (not the installation tree), type<\/li>\n<\/ul>\n
make clean<\/span><\/div>\n\n- To clean part of AAPP (e.g. AAPP, metop-tools, iasi-tools or a lower-level module), go to the appropriate directory and type<\/li>\n<\/ul>\n
make clean<\/span><\/div>\n\n- To clean the object files of AAPP (or metop-tools, or iasi-tools), leaving the data files and executables unchanged (this can be useful on operational systems), go to the AAPP, metop-tools or iasi-tools directory and type<\/li>\n<\/ul>\n
make clean_obj<\/span><\/div>\n\n- To re-build a lower-level module of AAPP (e.g. amsubcl), cd to the appropriate library (e.g. AAPP\/src\/calibration\/libamsubcl) and type<\/li>\n<\/ul>\n
make lib
\ncd ..\/bin
\nmake bin<\/div>\n
\n- To re-install selected data files, cd to the sub-directory of src<\/span> that contains the\u00a0data
\nfile and type<\/li>\n<\/ul>\nmake dat<\/span><\/div>\n\n- AAPP is delivered with Makefiles already supplied. To re-generate all makefiles (e.g. if you have added a module), go to the top directory and type<\/li>\n<\/ul>\n
perl makefile.PL<\/span><\/div>\nIf make<\/em> fails because an external library is missing, locate the library and modify your Makefile.ARCH<\/span> or re-run configure<\/span>. Remember that -L<\/span> specifies the location of the library (if it is not in one of the standard directories) and -lx<\/span> links the library named libx.a<\/span>. For example, on the ECMWF AIX system, when building AAPP with HDF5 support it was necessary to add -lz<\/span> to link the centrally-installed zlib.
\nIf the make<\/span> fails for reasons that are not obvious, before re-trying it is recommended that you remove any partially installed components using make clean<\/span>. Similarly if having built AAPP you decide that you want to install the BUFR or GRIB libraries, then you can make clean<\/span>, re-run configure<\/span>, then re-run make.
\n<\/span><\/p>\nThe ATOVS_ENV8 file<\/h3>\n
In AAPP v1 to v5 the ATOVS_ENV file that sets up the AAPP environment was always located in the user’s $HOME directory. This caused problems for some users and made it difficult to run different versions of AAPP simultaneously. For AAPP v6 the system was changed, and it is the same in AAPP v7 and v8:<\/p>\n
\n- The script that sets up the environment is\u00a0called ATOVS_ENV8.<\/li>\n
- ATOVS_ENV8 is created in the installation directory by the configure<\/span> script.<\/li>\n
- Also in the AAPP installation directory is a file called ATOVS_CONF. This file is run by all the built-in AAPP scripts.<\/li>\n
- When ATOVS_CONF is called it first looks for an ATOVS_ENV8 file in $HOME. If one exists, it will be used.<\/li>\n
- If there is no $HOME\/ATOVS_ENV8 then the ATOVS_ENV8 file in the AAPP installation directory will be used.<\/li>\n<\/ul>\n
The user may if required move the ATOVS_ENV8 file to his $HOME directory (or create a link). Then to set up the environment for AAPP the user’s script (or interactive shell) needs:<\/p>\n
. $HOME\/ATOVS_ENV8
\n<\/span><\/div>\nAlternatively the user’s script may source ATOVS_CONF:<\/p>\n
AAPP_PREFIX=…….
\n. $AAPP_PREFIX\/ATOVS_CONF
\n<\/span><\/div>\nIn either case all the AAPP scripts and binaries (including those in metop-tools and iasi-tools) will then be accessible by name, since ATOVS_ENV8 sets up $PATH to include the necessary directories.<\/p>\n
You may need to edit the ATOVS_ENV8 file after it has been created by configure<\/span> – e.g. to set the correct path for the GMT<\/span> executables (rarely used these days) and to set $LD_LIBRARY_PATH for use with HDF5 or ecCodes. Note that older versions of the HDF5 library (5-1.8.1 and earlier) required the SZIP library to be centrally installed or included in $LD_LIBRARY_PATH.<\/p>\nSpecial considerations for Windows PC installation<\/h3>\n
Previous versions of the AAPP Installation Guide gave hints on running AAPP under (i) Microsoft Windows Services for Unix (SFU) and (ii) Microsoft\u00a0Subsystem for UNIX-based Applications (SUA). However, these are considered obsolete so those sections have been removed. It may still be possible to run AAPP under Cygwin, but this has not been tested by the NWP SAF. The notes made some years ago are included below.<\/p>\n
Cygwin is available from http:\/\/www.cygwin.com\/<\/a>.As well as standard utilities, you need to install perl, a korn shell (pdksh.exe) and a suitable Fortran compiler. The following changes are needed:<\/p>\n\n- Ensure the LIB environment variable (echo $LIB<\/span>) does not contain any Windows path names with colons or spaces, otherwise make<\/span> will fail. You can nullify this variable by typing:<\/li>\n<\/ul>\n
LIB=<\/div>\n
\n- The AAPP scripts require that the korn shell executable exists as \/bin\/ksh. So create a link as follows<\/li>\n<\/ul>\n
ln -s \/bin\/pdksh.exe \/bin\/ksh<\/span><\/div>\n\n- You should use the \u2212\u2212scriptdir=scripts<\/span> option in configure<\/span>. If you do not then the scripts will not be installed; this is because Cygwin will not create prog<\/span> if prog.exe<\/span> already exists in the same directory.<\/li>\n<\/ul>\n
\n- Having run configure<\/span>, ensure that your PATH definition in ATOVS_ENV8 does not contain any Windows path names with spaces. Edit ATOVS_ENV8 if necessary.<\/li>\n<\/ul>\n
\n- On some systems, make<\/span> fails because it does not recognise “\\cp” in the Makefiles. If this is the case, edit Makefile.PL<\/span>,
\nchange “\\cp” to ” cp”, change “\\rm” to ” rm” and “\\mkdir” to ” mkdir” (i.e. space instead of \\). Then type<\/li>\n<\/ul>\nperl Makefile.PL<\/span><\/div>\nAAPP directory structure<\/h3>\n
After the successful installation of AAPP on your machine you should find on your system the following AAPP directory structure:
\n.\/AAPP
\n.\/AAPP\/bin
\n.\/AAPP\/gmt
\n.\/AAPP\/include
\n.\/AAPP\/lib
\n.\/AAPP\/man
\n.\/AAPP\/man\/man1
\n.\/AAPP\/man\/man3
\n.\/AAPP\/man\/man5
\n.\/AAPP\/module
\n.\/AAPP\/orbelems
\n.\/AAPP\/orbelems\/ephe
\n.\/AAPP\/orbelems\/orb_elem
\n.\/AAPP\/orbelems\/satpos
\n.\/AAPP\/orbelems\/tbus_db
\n.\/AAPP\/orbelems\/tbus_db\/2010-03
\n.\/AAPP\/orbelems\/tracking
\n.\/AAPP\/src
\n.\/AAPP\/src\/calibration
\n.\/AAPP\/src\/calibration\/bin
\n.\/AAPP\/src\/calibration\/libamsuacl
\n.\/AAPP\/src\/calibration\/libamsubcl
\n.\/AAPP\/src\/calibration\/libavhrcl
\n.\/AAPP\/src\/calibration\/libcal
\n.\/AAPP\/src\/calibration\/libhirscl
\n.\/AAPP\/src\/calibration\/libhirscl_algoV4
\n.\/AAPP\/src\/calibration\/libmhscl
\n.\/AAPP\/src\/calibration\/libmsucl
\n.\/AAPP\/src\/decommutation
\n.\/AAPP\/src\/decommutation\/bin
\n.\/AAPP\/src\/decommutation\/libdecom
\n.\/AAPP\/src\/libauxaapp
\n.\/AAPP\/src\/libbufrdummy
\n.\/AAPP\/src\/maia4
\n.\/AAPP\/src\/maia4\/bin
\n.\/AAPP\/src\/maia4\/libaapp_viirs
\n.\/AAPP\/src\/maia4\/libavhrrin_tools
\n.\/AAPP\/src\/maia4\/libmaia4
\n.\/AAPP\/src\/maia4\/libmaia4IO
\n.\/AAPP\/src\/maia4\/libmapviirscris
\n.\/AAPP\/src\/navigation
\n.\/AAPP\/src\/navigation\/bin
\n.\/AAPP\/src\/navigation\/libMSLIB77_V3.1
\n.\/AAPP\/src\/navigation\/libbrolyd
\n.\/AAPP\/src\/navigation\/libephtrack
\n.\/AAPP\/src\/navigation\/libnavnoaa
\n.\/AAPP\/src\/navigation\/libnavtool
\n.\/AAPP\/src\/navigation\/libsgp
\n.\/AAPP\/src\/navigation\/libtbus
\n.\/AAPP\/src\/navigation\/libtle
\n.\/AAPP\/src\/preproc
\n.\/AAPP\/src\/preproc\/bin
\n.\/AAPP\/src\/preproc\/libatov
\n.\/AAPP\/src\/preproc\/libatovin
\n.\/AAPP\/src\/preproc\/libatovpp
\n.\/AAPP\/src\/preproc\/libavh2hirs
\n.\/AAPP\/src\/preproc\/libmappiasi
\n.\/AAPP\/src\/tools
\n.\/AAPP\/src\/tools\/bin
\n.\/AAPP\/src\/tools\/libaappbufr
\n.\/AAPP\/src\/tools\/libaapphdf5
\n.\/AAPP\/src\/tools\/libf7cp
\n.\/AAPP\/src\/tools\/libf7gp
\n.\/AAPP\/src\/tools\/libf7ml
\n.\/AAPP\/src\/tools\/libf7nl1b
\n.\/AAPP\/src\/tools\/libf7tp
\n.\/AAPP\/src\/tools\/libsatid
\n.\/AAPP\/src\/tools_eccodes
\n.\/AAPP\/src\/tools_eccodes\/bin
\n.\/AAPP\/src\/tools_eccodes\/libecbufr
\n.\/config
\n.\/iasi-tools
\n.\/iasi-tools\/bin
\n.\/iasi-tools\/include
\n.\/iasi-tools\/lib
\n.\/iasi-tools\/man
\n.\/iasi-tools\/src
\n.\/iasi-tools\/src\/bin
\n.\/iasi-tools\/src\/libcnes_iasi_brd_1.6
\n.\/iasi-tools\/src\/libcnes_iasi_brd_1.7
\n.\/iasi-tools\/src\/libcnes_iasi_ctx_1.2
\n.\/iasi-tools\/src\/libcnes_iasi_grd_1.6
\n.\/iasi-tools\/src\/libcnes_iasi_grd_1.7
\n.\/iasi-tools\/src\/libcnes_iasi_odb_1.4
\n.\/iasi-tools\/src\/libeps_iasil1b_6.6
\n.\/iasi-tools\/src\/libeps_iasil1b_9.0
\n.\/iasi-tools\/src\/libeps_iasil1c_6.6
\n.\/iasi-tools\/src\/libeps_iasil1c_9.0
\n.\/metop-tools
\n.\/metop-tools\/bin
\n.\/metop-tools\/include
\n.\/metop-tools\/lib
\n.\/metop-tools\/man
\n.\/metop-tools\/src
\n.\/metop-tools\/src\/bin
\n.\/metop-tools\/src\/libaapp_avhrrl1b
\n.\/metop-tools\/src\/libaapp_avhrrl1c
\n.\/metop-tools\/src\/libccsds
\n.\/metop-tools\/src\/libeps_avhrrl1b_6.5
\n.\/metop-tools\/src\/libeps_common
\n.\/metop-tools\/src\/libeps_metopl0
\n.\/metop-tools\/src\/libmetop_amsua
\n.\/metop-tools\/src\/libmetop_avhrr
\n.\/metop-tools\/src\/libmetop_common
\n.\/metop-tools\/src\/libmetop_hirs
\n.\/metop-tools\/src\/libmetop_intex
\n.\/metop-tools\/src\/libmetop_mhs
\n.\/metop-tools\/src\/libmetop_mmam
\n.\/metop-tools\/src\/libobtutc<\/p>\n
In the run-time directory $AAPP_PREFIX (if applicable) you will find:
\n.\/AAPP\/
\n.\/AAPP\/bin\/
\n.\/AAPP\/lib\/
\n.\/AAPP\/include\/
\n.\/AAPP\/data\/
\n.\/metop-tools\/
\n.\/metop-tools\/bin\/
\n.\/metop-tools\/lib\/
\n.\/metop-tools\/include\/
\n.\/iasi-tools\/
\n.\/iasi-tools\/bin\/
\n.\/iasi-tools\/lib\/
\n.\/iasi-tools\/include\/<\/p>\n
TLE files for the test cases are provided as part of the test case. For running with your own HRPT data you should create the following directories: ${DIR_NAVIGATION}\/tle_db<\/span> and\/or ${DIR_NAVIGATION}\/tbus_db<\/span> (where DIR_NAVIGATION<\/span> is defined in ATOVS_ENV8<\/span>) and place your TBUS or TLE files in monthly subdirectories. In the case of TLE, the “get_tle” script does all this automatically, creating directories as required.<\/p>\nAfter installation<\/h3>\n
After you have executed the installation procedure a few steps have to be performed before you can go to run AAPP:<\/p>\n
\n- Check whether your installation was successful. Note that the error messages from the Fortran compilations might differ depending on the compiler you are using. Some compilation warnings are to be expected, but you should not see any actual errors. The “make” process will terminate early if there is an error.<\/li>\n
- If you have customised the configuration file (e.g. are using a different compiler from those that are supported), it is advisable to run the tools
![\"NWP](\"https:\/\/nwp-saf.eumetsat.int\/images\/NWPSAFLogo_gradient_S.png\")
<\/h1>\n