As discussed a few days ago, I have just committed corrections to the schedule.ccl of various thorns. If you update any of these thorns, then you need to update MoL and several other thorns as well -- otherwise you will have an inconsistent schedule, and time evolution will be gravely inconsistent. (If you fail to update, you are supposed to see an error message.)
In particular, I corrected the schedules of - GRHydro - ML_ADMConstraints - ML_AMDQuantities - ML_BSSN - NaNChecker
and these corrections crucially depend on the thorns - Carpet - (Kranc -- only when you generate code yourself) - MoL - TmunuBase
These schedule corrections ensure consistency during checkpointing and recovery, and correct a few other minor spots. In particular, if you checkpoint and recover, you should now see identical results (except for the pressure, which depends on the con2prim accuracy). Previously, certain operations were missing or were applied twice after recovering, leading e.g. to "weird" constraint values for the next few coarse grid time steps. To my knowledge, the evolution variables themselves were already consistent after recovery up to floating-point round-off (and up to con2prim accuracy).
-erik
On 3 Aug 2011, at 02:57, Erik Schnetter wrote:
As discussed a few days ago, I have just committed corrections to the schedule.ccl of various thorns. If you update any of these thorns,
Some of the Einstein Toolkit tests in the test suite are now failing (both with stable and development (git and mercurial) versions of Carpet):
Hydro_InitExcision/* ML_BSSN_sgw3d KerrSchild-rotating-180 KerrSchild-rotating-90
Some of the other tests failed on 3rd August but passed on 4th August. The tests run at 1am CET, which might have been about the time that Erik was committing, so it may have been due to an inconsistent checkout. Alternatively, maybe someone fixed them.
http://damiana2.aei.mpg.de/~ianhin/testsuites/einsteintoolkit/
If you want to run the test suite yourself, you can easily do so using SimFactory (version 2):
sim create-run mytests_1proc --testsuite --procs 1 sim create-run mytests_2proc --testsuite --procs 2
It takes a couple of hours to run all the tests, as far as I remember. You can also run specific tests using
sim create-run mytests_1proc --testsuite --select-tests <test> --procs 1
where <test> is either <testname>.par, <arrangement> or <arrangement>/<thorn>.
If you want to run on a cluster, replace create-run with create-submit, and add a --walltime option. You may also have to request --procs <n>, where <n> is a multiple of the number of cores on each node, and then use --ppn-used 1 to indicate that only one processor (core) is used on each node - this is only necessary on some machines; on other machines, simfactory knows to request the correct number of cores and then only use the number you asked for.
Details are also given in the (work-in-progress) user guide for SimFactory, a snapshot of which is currently at http://www.aei.mpg.de/~ianhin/simfactory-userguide/. Specifically, see the section http://www.aei.mpg.de/~ianhin/simfactory-userguide/use.html#running-the-test....
users@lists.einsteintoolkit.org
-
Erik Schnetter -
Ian Hinder