From 3b4da5fbe21f141fbcd8fa69cf8d1c0759dd208d Mon Sep 17 00:00:00 2001 From: rhaas Date: Sat, 25 May 2013 17:40:10 +0000 Subject: add parameter to disable MoL_PostStep in Post_Recover_Variables this is to allow bit-wise recovery of Hydro data since con2prim runs in MoL_PostStep. Also we should be able to read in all data from a checkpoint and thus mol_poststep should not be required. Thorns that want to be clever and re-compute some quantities that can be recomputed from the checkpointed data should schedule themselves explicitly in Post_Recover_Variables. See extensive discussion at https://trac.einsteintoolkit.org/ticket/1256 git-svn-id: http://svn.cactuscode.org/arrangements/CactusNumerical/MoL/trunk@199 578cdeb0-5ea1-4b81-8215-5a3b8777ee0b --- schedule.ccl | 2 ++ 1 file changed, 2 insertions(+) (limited to 'schedule.ccl') diff --git a/schedule.ccl b/schedule.ccl index 6d607ba..44f9b6d 100644 --- a/schedule.ccl +++ b/schedule.ccl @@ -706,9 +706,11 @@ schedule GROUP MoL_PostStep AT PostRestrict ### expensive, but it's simplest for the moment. ### ############################################################## +if(run_MoL_PostStep_in_Post_Recover_Variables) { schedule GROUP MoL_PostStep AT Post_Recover_Variables { } "Ensure that everything is correct after recovery" +} ######################################################################### ### Physics thorns can enforce constraints in PostStepModify. ### -- cgit v1.2.3