source: anuga_validation/automated_validation_tests/README.txt @ 7276

Last change on this file since 7276 was 7276, checked in by ole, 15 years ago

Merged numpy branch back into the trunk.

In ~/sandpit/anuga/anuga_core/source
svn merge -r 6246:HEAD ../../branches/numpy .

In ~/sandpit/anuga/anuga_validation
svn merge -r 6417:HEAD ../branches/numpy_anuga_validation .

In ~/sandpit/anuga/misc
svn merge -r 6809:HEAD ../branches/numpy_misc .

For all merges, I used numpy version where conflicts existed

The suites test_all.py (in source/anuga) and validate_all.py passed using Python2.5 with numpy on my Ubuntu Linux box.

File size: 1.2 KB
Line 
1This directory, automated_validation_tests, contains a collection of
2projects that validate ANUGA against known scenarios either from physical
3observations or analytical solutions.
4
5The validation tests take the form of automated unit tests except that they
6all test the whole system rather than individual components and that they
7generally take considerably longer time to execute than normal unittests.
8
9The master script, validate_all.py, will run through all tests. 
10
11NOTE: In some circumstances there may be problems running validate_all.py
12IF MORE THAN ONE PYTHON IS INSTALLED.  The workaround is to:
131. Decide which python you want to use, and get the absolute path to that
14   executable ('which python2.5', for example)
152. Create a local 'bin' directory:
16       mkdir ~/bin
173. Create a 'python' link in that directory to the python executable:
18       ln -s ~/bin/python <path_from_step_1>
194. Create or modify your PATH variable in ~/.bashrc to include:
20       export PATH=$HOME/bin:$PATH
21   That is, ensure your 'local' bin is searched first
225. Remove any 'python' alias you may have defined in ~/.bashrc (or elsewhere)
236. Ensure all the above changes are in effect by opening a new terminal
24
25The above workaround was tested under Linux.  Not sure about Windows.
Note: See TracBrowser for help on using the repository browser.