Changeset 7039

Timestamp:

May 14, 2009, 3:17:59 PM (15 years ago)

Author:

rwilson

Message:

Back-merge changes from the Numeric trunk.

Location:

branches/numpy_anuga_validation

Files:

• automated_validation_tests/okushiri_tank_validation/test_caching_of_set_quantity.py (added)
• automated_validation_tests/patong_beach_validation/run_model.py (modified) (1 diff)
• automated_validation_tests/patong_beach_validation/validate.py (modified) (1 diff)
• okushiri_2005/test_caching_of_set_quantity.py (modified) (1 diff)

branches/numpy_anuga_validation/automated_validation_tests/patong_beach_validation/run_model.py

@@ -75 +75 @@
 
 # Create the STS file
+# FIXME (Ole): This is deadly dangerous if buildcode changes (as was the case 24th March 2009)
+# We need to use caching instead!
+
 log.critical( 'project.mux_data_folder=%s' % project.mux_data_folder)
 if not os.path.exists(project.event_sts + '.sts'):

branches/numpy_anuga_validation/automated_validation_tests/patong_beach_validation/validate.py

@@ -47 +47 @@
 Optional_Data_Objects = ('patong.sww.TRIAL.tgz',
                          'patong.sww.BASIC.tgz',
-                         'patong.sww.FINAL.tgz',
+                         'patong.sww.FINAL.tgz'
                         )
 

branches/numpy_anuga_validation/okushiri_2005/test_caching_of_set_quantity.py

@@ -1 @@
-"""This script tests that caching works for set_quantity using point data from a file.
+"""This script tests that caching works for set_quantity using point 
+data from a file.
 First cache is cleared, then set_quantity is run twice checking that
 fitting is evaluated only first time and that the result from cache on the