Changes between Version 52 and Version 53 of TestSuite

Timestamp:

11/30/11 12:28:37 (13 years ago)

Author:

ehansen

Comment:

—

TestSuite

@@ -3 +3 @@
 The basic design philosophy has been simplified from the old version of the test suite.  The test suite is essentially a group of problem modules that are automatically compiled and run in alphabetical order.  Each problem tests a different part of the astrobear code.
 
-== Current testing (6/30/11, under edition) ==
-At the moment we do post-processing tests of astroBEAR2.0. Basically, tests consist on comparing the flow variables in a chombo file produced by the test modules, against a ''reference chombo file'' (see below).
+== Current Testing ==
+At the moment we do post-processing tests of AstroBEAR 2.0. Basically, tests consist on comparing the flow variables in a chombo file produced by the test modules, against a ''reference chombo file'' (see below).
 All test related files are located in modules/tests/.
 Each test has its own directory which contains: 
 - the problem's data files: global.data, modules.data, problem.data, profile.data, solver.data, communication.data, io.data and physics.data,
 - the problem's module problem.f90,
-- two data files used by BearToFix to produce test reports:  bear2fix.data.test and bear2fix.data.img,
+- two data files used by bear2fix to produce test reports:  bear2fix.data.test and bear2fix.data.img,
 - a "ref" directory which contains the reference chombo file.
 
@@ -16 +16 @@
 '''Running tests'''. This is done using two shell scripts:
 - postprocess.s, that iterates over each of the test problem and calls the go.s script,
-- go.s, which basically cd's into the current test directory and executes BearToFix (see below), converts the images from ps to png and copies them back into the image directory. These images will them be linked to the corresponding test report wiki pages.
+- go.s, which basically cd's into the current test directory and executes bear2fix (see below), converts the images from ps to png and copies them back into the image directory. These images will then be linked to the corresponding test report wiki pages.
 
-'''Tests report'''. Once test runs are finished, BearToFix will be executed. It will do the error computations and produce two png images showing the reference and the current result of the run. BearToFix is executed twice; the 1st time it reads bear2fix.data.img to set the color tables for the test report images, whereas the 2nd time it reads bear2fix.data.test to perform the error computation and produce the test report images. 
+'''Tests report'''. Once test runs are finished, bear2fix will be executed. It will do the error computations and produce a png image showing the current result of the run. bear2fix is executed twice; the 1st time it reads bear2fix.data.img to set the color tables for the test report image, whereas the 2nd time it reads bear2fix.data.test to perform the error computation and produce the test report errors. 
 
-'''Tests error calculations'''. These are done in BearToFix via L2norms and LInfinity norms (reference to be added soon).
+'''Tests error calculations'''. These are done in bear2fix via comparing the fluid variable information contained in the chombos.  See the section below the list of tests for a more detailed description.
 
-To use BearToFix by yourself (e.g. in order to do further adjustment of the test report parameters), select operation 11, test 4 (Generic Test) and input the maximum mean error tolerance (see below) allowed for each fluid variable. BearToFix will then compute the errors and produce the test report images. You should then copy these images to the test images directory (reference to be added soon).
+'''If the test fails''', The test will fail if one of the relative errors calculated is greater than 5%. Inspection of the text report wiki page should show why the test failed.
 
-'''If the test fails''', BearToFix outputs the current errors as well as suggested new tolerances (5% higher than the current errors). The user can then copy and paste these figures into the bear2fix.data.test file and run BearToFix again. Inspection of the text report wiki page should show why the test failed.
+'''The test log file''' is located in the data/tests directory on clover and briefly keeps track of test results.
 
-'''The test log file''' is located in the modules/tests directory and briefly keeps track of test results. We plan to add the log info into the test report images though the convert command, so the user can see the images and the error estimates at once.
+
+== ***Wiki Integration Coming Soon*** ==
 
 == List of tests ==
@@ -39 +40 @@
 ||= 1D Sod Shock Tube [wiki:TestSuite/SodShockTube] =||= Runs 1D Sod shock tube with all combinations of integration schemes =||= None =||= 60 sec. (single-proc, grass) =||= In Development (Eddie) =||
 ||= 2D Rayleigh-Taylor Instability [wiki:TestSuite/RayleighTaylor2D] =||= A heavy fluid above a light fluid with uniform gravity is perturbed. =||= None =||= Approx 11 minutes (4-proc, alfalfa) =||= Implemented =||
-||= Bondi-Hoyle Accretion [wiki:TestSuite/Bondi] =||= Spherically symmetric accretion of gas =||= None =||= ??? =||= In Development (Ruka) =||
+||= Bondi-Hoyle Accretion [wiki:TestSuite/Bondi] =||= Spherically symmetric accretion of gas =||= None =||= ??? =||= Implemented =||
 ||= Orbiting Particles [wiki:TestSuite/OrbitingParticles] =||= 2 particles orbiting each other =||= None =||= ??? =||= In Development (Eddie) =||