IMPORTANT: Added test cases to the repository

[arango]

There has been a lot of traffic in the forum of users struggling how to configure the Test Cases distributed in ROMS. Notice that we introduced last year the test svn repository:

URL:  https://www.myroms.org/svn/src/test

It includes the sub-directory WC13 showing how to run all the 4D-Var algorithms available in ROMS and documented in ​WikiROMS tutorial.

Now I adding several directories which include more Test Cases:

test/
     DAMEE_4/
            /Data/
                 /netcdf3
                 /netcdf4
            /scoord11
            /scoord22
     External/
     WC13/
         /ARRAY_MODES
         /Data
         /Functionals
         /I4DVAR
         /I4DVAR_impact
         /Normalization
         /PSAS
         /PSAS_impact
         /PSAS_sensitivity
         /R4DVAR
         /R4DVAR_impact
         /R4DVAR_sensitivity
         /plotting
     basin/
     benchmark/
     bio_toy/
            /Data
     bl_test/
     canyon/
     double_gyre/
                /AFTE
                /Data
                /FSV
                /FTE
                /Forward
                /OP
                /SOsemi
     estuary_test/
     flt_test/
     grav_adj/
     inlet_test/
               /Data
     kelvin/
     lab_canyon/
     lmd_test/
     riverplume/
     seamount/
     sed_test/
     shoreface/
     soliton/
     test_chan/
     test_head/
              /Data
     upwelling/
     weddell/
     windbasin/

• Notice that there is a directory for each Test Case. The realistic applications are in uppercase whereas the idealized applications are in lowercase. There is also an External sub-directory containing the metadata files varinfo.dat and coupling.dat.

• Each sub-directory contains the necessary header file, standard input scripts, configuration scripts, and build scripts to compile, link, and run each application.

• All the sub-directories show the build script in all its glory. It provides examples of how to manipulate ROMS c-preprocessing options without the need of changing the makefile and/or application header file. Users can start playing with several combinations of the CPP options. Be aware that when making changes it may require the fine-tuning of the application time-step to satisfy CFL constraint.