Skip to content

Latest commit

 

History

History
68 lines (53 loc) · 2.03 KB

testing.md

File metadata and controls

68 lines (53 loc) · 2.03 KB

Testing

Extpar is tested with an adapted version of the COSMO technical testsuite.

Run Tests

First step is to compile the code following the instructions in compile_run.

Daint

cp bin/* test/testsuite/bin/.
cd test/testsuite
./data/get_data.sh
./bin/extract_inputfiles_from_namelist.py
sbatch --wait ./submit.daint.transfer.sh
sbatch submit.daint.sh

Tsa

cp bin/* test/testsuite/bin/.
cd test/testsuite
./data/get_data.sh
./bin/extract_inputfiles_from_namelist.py
sbatch --wait ./submit.tsa.transfer.sh
sbatch submit.tsa.sh

Levante

cp bin/* test/testsuite/bin/.
cd test/testsuite
./data/get_data.sh
sbatch submit.levante.sh

The results of the testsuite can be found in file testsuite.out

An example output could look as follows:
Testsuite_log

Testlists

There are many different testlist, each containing a set of tests for different setups, compiler or models:

GCC

Tolerances

It is possible to define an optional tolerance threshold for each test and each field. To allow deviations for the test icon_d2 for example, just dit the the tolerances-file. The syntax is as follows:

PARAMETER, abs_diff
NDVI, 9.0e-08
W_SNOW, 5.0e-05

Add a new test

  1. Modify the testlist.xml file to add the new test. Alternatively, you could also add a new testlist XML file (with a new name). The testlist which is run can be chosen from the testsuite command line.

  2. Make a folder in the data folder for the new test containing the INPUT_* files and the namelist.py for the Python-CDO modules.

  3. Send any binary reference files to upload to the ftp site to the source code administrator.