#5 All examples work as off 2113-04-18

[Anonymous]

Originally created by: tolstho...@gmail.com
Originally owned by: tolstho...@gmail.com

As users experienced, a number of examples failed. This was due to lack of backward compatibility. During the first half of April 2013, I went through all them, modernising where necessary, removing obsolete stuff and removing redundancy. Wherever necessary I upgraded existing functions, uniforming style and attempting to make them more robust.

mfLab has a few new directories, which you automatically get when you do an update in SVN. One of them is mflab/mfiles/testsuites in which you find some functions that allow you to run any examples in the directory tree downward from and including the node where you start it. There is one that only runs the mf_adapt and mf_build mfiles it can find. And there is one that searches all m-files for the use of a given string. This can be used to find a certain use of a given functions anywhere in the directory tree. These functions leave a message behind in the respective directories, telling whether the test failed and when to redo the test. It is not doing the same test each time you run the function unless you tell it so or unless the date for retesting has passed.
These functions may not be perfect, but they helped me enormously to achieve the heavy task of verifying every existing example. You may add the testsuites directory to the path. Here are the paths that I have in my shortcut.

% Shortcut summary goes here
pathstr = '~/GRWMODELS/mflab/mfiles/';
addpath([pathstr 'write']);
addpath([pathstr 'read']);
addpath([pathstr 'etc']);
addpath([pathstr 'analytic']);
addpath([pathstr 'visualization']);
addpath([pathstr 'gridcoords']);
addpath([pathstr 'fdm']);
addpath([pathstr 'NHI']);
addpath([pathstr 'testSuites']);
fprintf('... mfLab paths set.\n');

Theo Olsthoorn 2013-04-18