- Supported platforms: UNIX or Linux platforms, 32-bit or 64-bit.
- Software requirements: KORN shell, FORTRAN 77 or FORTRAN 90 compiler, C compiler, make, gunzip, gzip, tar, perl5. The optional OPS-LRS (for IASI processing) also requires a C++ compiler and support for posix threads. OPS-LRS requires perl_5.16 or earlier (if you want to use a later version of perl, see instruction in item 17 on the bugs page).
- To make use of the full functionality of AAPP, you will need to install various external packages (e.g. ECMWF BUFR library and the HDF5 library). For details, please see the Installation Guide.
- Disk space requirements: the AAPP/OPS-LRS software and data files occupy about 9GB of disk space (or 4GB if you don’t need to run MAIA4, the VIIRS cloud mask).
- Memory requirements: there are no special requirements to run the core parts of AAPP (e.g. ATOVS/AVHRR processing). IASI processing requires at least 2GB of memory, but runs faster on systems with more memory, because more threads can be used. We recommend at least 6GB.
- Distribution policy: distribution is free of charge to anyone who agrees to the licence conditions contained in the Licence Agreement.
How to get a copy of the AAPP software system
Software package downloads are now managed in the User Area. You must first register on the site and then go to your user area once logged in. Click ‘Change Software Preferences‘ to edit your software package downloads. Software packages are provided free of charge subject to a licence agreement.
Supplementary downloads are available via an ftp site. There you can find test cases, OPS-LRS auxiliary data, MAIA data files and ATOVS calibration files. You can also find there a script install_aapp8.sh that can be used to build AAPP and its dependencies.
To make it easier for users to download OPS-LRS auxiliary data, a shell script, get_aux_files.sh, is available. Download the script, give it execute permission (chmod +x get_aux_files.sh) and run it on your system. Type ./get_aux_files.sh to see the usage instructions. You need to specify a destination directory where the files are to be placed, and you can optionally specify the satellites of interest (M01, M02, M03) and a validity date. The date defaults to today but you can specify an earlier date for historic cases (including the supplied test case). The script only attempts to download files that are not already in the destination directory, so you can, if you wish, run it routinely (e.g. weekly) to check for new auxiliary files.
In the same way, a script get_atovs_cal_files.sh can be used to check whether your ATOVS calibration files are up to date. Normally these files are included in AAPP software releases, but sometimes they need to be updated at short notice.