Difference between revisions of "Glam:testing"
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
* NC_DIR in the makefile points to a valid netcdf installation for your compiler. | * NC_DIR in the makefile points to a valid netcdf installation for your compiler. | ||
| − | =Running the test script= | + | |
| + | ==Running the test script== | ||
The test script can be run using the makefile as follows: | The test script can be run using the makefile as follows: | ||
| Line 16: | Line 17: | ||
| − | =Further plans= | + | ==Further plans== |
* automate the test as part of a nightly build (probably on one of the Bristol machines) | * automate the test as part of a nightly build (probably on one of the Bristol machines) | ||
Revision as of 13:28, 3 July 2008
The glam respository now contains a test script to provide a quick check for whether code changes impact on model output. The comparison is based on output files from glam in netcdf format.
The test script is valid if the following hold:
- The GLAM/knowngood/glam_2d.nc file contains up to date known good velocity fields.
- NC_DIR in the makefile points to a valid netcdf installation for your compiler.
Running the test script
The test script can be run using the makefile as follows:
make test
This will build the executable GLAM/nccompare.exe (from compare.cpp) and run the test script GLAM/test.sh
Further plans
- automate the test as part of a nightly build (probably on one of the Bristol machines)
- make the netcdf output filename a namelist option
- create further tests, with a namelist file providing configuration information for each, and build these into the test script.
- add fields to the netcdf outputting as needed