BISMG:SarahS/automated testing

Set up EISMINT-1 and hump tests on the lanl/trunk and the lanl/parallel branch

the total size of the check out is 120.5kb. The GS files must not make this much larger.
 * STEP 1. Generate the golden standard files. Note that the GS generated by glimmer-cism/trunk for e1.mm.1.nc differs to that generated by glimmer-cism/lanl/trunk. The wvel(surface) differs by +/- 0.5myr-1.


 * STEP 2. Add compare.cpp to tests/util/

svn ci -m "ggsrs: Add tool to compare two netCDF files for automated nightly build and standard tests" compare.cpp

svn ci -m "ggsrs: Add EISMINT-1 configuration files for automated nighly build and tests. Files have been modified to reduce the size of the output. See README " EISMINT-1
 * STEP 3. upload the EISMINT-1 tests to /tests


 * STEP 4. * Get autoconf to build compare.cpp
 * In configure.in at line 35 insert: AC_PROG_CXX This finds the cpp compiler
 * In configure.in at line 165 insert: CXXFLAGS="$FCFLAGS $ax_cv_f90_modflag$ac_cv_netcdf_prefix/include" . This links compare.cpp to the netCDF directory
 * In configure.in at line 349 add tests/util/Makefile to the list of AC_CONFIG_FILES
 * In /test/util create a Makefile.am (a Makefile template) which compiles compare.cpp. Makefile.am contains the lines

bin_PROGRAMS = compare compare_SOURCES = compare.cpp compare_LDADD= -lnetcdf_c++
 * In /glimmer-prefix/Makefile.am add tests/util to the list like this SUBDIRS= m4macros src tests/util.


 * STEP 5. Run autoreconf to remake the Makefiles.in


 * STEP 6. Re-run ./configure --prefix=/data/ggsrs/glimmer-test --with-netcdf=/opt/local/CentOS-64/netcdf/4.0/intel_fc_10.1 FC=ifort F77=ifort


 * STEP 7. compare.cpp will now be made when we type make.

test:: newline and tab ${prefix}/tests/util/test.sh ${prefix} ${FC} ${experiment_type} ${experiment_number}
 * STEP 8. Get autoconf to create a new target so that typing "make tests  " invokes the test script. In /glimmer_prefix/Makefile.am


 * STEP 9. Use the script by typing: make test exp_type=eismint-1 exp_num=1

Feed the script some arguments

To do;
 * 1. plot EISMINT-1 GS files and compare to EISMINT-1 paper (1996, Payne)
 * 1. Get greenland and climate input to test glint.
 * 2. Change file permissions in test_suite dir
 * 3. compile nccompare.cpp
 * 4. run nightly build on holocene include email alert
 * 5. output bmlt in EISMINT-2 short
 * 6. generate GS files (original + short) for EISMINT-1 fm expt1-3. Only created GS for mm experiments so far.


 *  Tests suggested by Bill Wilscombe 


 * EISMINT-1. In these tests the temperature does not interact with the velocity. i.e the viscosity is held constant. These tests mean the temperature code can be tested directly. The subsets to run are moving margin, steady state experiments. Variables to compare are thk, wvel, xvel, yvel, temp. Output every 40ky. this reduce the files from 109Mb to 1.93kB


 * EISMINT-2 In these tests the temperature and velocity interact. T.P suggests running (a) and (g) as these are steady state experiments. Compare the same variables as EISMINT-1 plus melt rate. (file size reduces from 1.18GB to 31Mb


 * ISMIP-HOM (a subset of tests A through F, for higher-order models only)


 * Ross ice shelf (for shelf and/or HO models)


 * the "hump" test on the parallel branch


 * one or more analytical tests, as in the Bueler papers. To this test aside for the time being. It is more a test of the physics of the model rather than if the code has broken


 * a glint-example test case for Greenland i.e demonstrate that the code can run for a long time without crashing


 * exact restart tests--very important for climate models. Put this aside for the time being.

Notes: ISMIP-HOM tests in glimmer-cism/glimmer-cism-lanl/trunk/ did not work. Verify.py created the same size netCDF files no matter which size is specified (--size=)

The EISMINT-1 tests

Write the test script in bash, keep in /home/automat'

Outline of the test script:

A rule in the makefile would invoke the script so that typing “make test  ” would run a test. Need help with this !!!!

The script then does the following


 * a. Check out the configuration files for the tests
 * b. Check out the golden standard files for the tests
 * c. Compile a tool to compare two neCDF files.
 * d. Run glimmer for each configuration file in the test.
 * e. Compare the output of the runs to the gold standard and report back if the tests passed or not.

The nightly build script checks out the code, builds it and runs the test script.


 * Automate the bash script by setting up a Cron job. If sending mail use holocene
 * On holocene open crontab using : crontab -e or (-l to list what is in crontab)
 * Alternatively, crontab file is located in /tmp
 * Specify the editor : export EDITOR=/usr/bin/emacs to get editor for crontab