diff options
author | hawke <hawke@578cdeb0-5ea1-4b81-8215-5a3b8777ee0b> | 2003-09-30 09:51:40 +0000 |
---|---|---|
committer | hawke <hawke@578cdeb0-5ea1-4b81-8215-5a3b8777ee0b> | 2003-09-30 09:51:40 +0000 |
commit | 1848ec75cf0a3aa3a03c8966f96e08f35f0f91c1 (patch) | |
tree | d422e03b16e22b7173af7015bc7c41cdf96db667 /schedule.ccl | |
parent | 2d958e593d3ad1939e95e483b3902de9ecb45093 (diff) |
Schedule PostStep in PostRestrict.
This may be expensive but should stop me wondering "Why does that symmetry boundary look wrong?" when using a new thorn with Carpet.
git-svn-id: http://svn.cactuscode.org/arrangements/CactusNumerical/MoL/trunk@35 578cdeb0-5ea1-4b81-8215-5a3b8777ee0b
Diffstat (limited to 'schedule.ccl')
-rw-r--r-- | schedule.ccl | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/schedule.ccl b/schedule.ccl index 0b151a2..a6bb2eb 100644 --- a/schedule.ccl +++ b/schedule.ccl @@ -304,6 +304,20 @@ schedule GROUP MoL_PostStep IN MoL_Step AFTER MoL_Add LANG: C } "The group for physics thorns to schedule boundary calls etc." +################################################################## +### Schedule the PostStep parts in the Carpet 'PostRestrict' ### +### bin so that symmetries are automatically done correctly. ### +### We may want to change this later as it could be ### +### expensive, but it's simplest for the moment. ### +### Note that if you compile without Carpet you will get a ### +### warning which you can ignore. ### +################################################################## + +schedule GROUP MoL_PostStep IN PostRestrict +{ + LANG: C +} "Ensure that everything is correct after restriction" + ################################################# ### Final internal MoL stuff; decrement the ### ### counter, change time and timestep ### |