From cb80cd36253bae64ac0e41432e36ce14358b5892 Mon Sep 17 00:00:00 2001
From: knarf <knarf@54511f98-0e4f-0410-826e-eb8b393f5a1e>
Date: Fri, 28 Apr 2006 08:49:04 +0000
Subject: only cosmetic (comments) changes

git-svn-id: http://svn.aei.mpg.de/numrel/AEIThorns/ADMMass/trunk@12 54511f98-0e4f-0410-826e-eb8b393f5a1e
---
 schedule.ccl | 27 ++++++++++++++-------------
 1 file changed, 14 insertions(+), 13 deletions(-)

(limited to 'schedule.ccl')

diff --git a/schedule.ccl b/schedule.ccl
index 089e683..bd64809 100644
--- a/schedule.ccl
+++ b/schedule.ccl
@@ -3,11 +3,12 @@
 
 STORAGE:ADMMass_LoopCounterG
 STORAGE:ADMMass_Masses
-#######################################################################################################
-# The storage of the following grid functions at all times is necessary only because carpet would 
-# allocate them only for the finest level, if the STORAGE specification were only in the ADMMass group,
-# as it was earlier. This will be changed back again, when carpet will be modified.
-#######################################################################################################
+###############################################################################
+# The storage of the following grid functions at all times is necessary only
+# because carpet would allocate them only for the finest level, if the STORAGE
+# specification were only in the ADMMass group, as it was earlier. This will
+# be changed back again, when carpet will be modified.
+###############################################################################
 STORAGE:ADMMass_GFs[3] 
 
 schedule ADMMass_InitLoopCounter AT INITIAL
@@ -28,14 +29,14 @@ schedule ADMMass_Loop IN ADMMass BEFORE ADMMass_Local
   OPTIONS: global
 } "Decrement loop counter"
 
-#########################################################################################
-# We must schedule the local routines to compute the integrals in global-loop-local 
-# (as opposed to local) mode, in order to make sure that the scheduling condition
-# "AFTER", which describes the ADMMass group, is respected. This group may depend 
-# on local routines (excision, emask) and must be run after all local routines. 
-# If we had no such a dependence, we could have scheduled the integral computations 
-# simply in local mode.
-##########################################################################################
+###############################################################################
+# We must schedule the local routines to compute the integrals in
+# global-loop-local (as opposed to local) mode, in order to make sure that the
+# scheduling condition "AFTER", which describes the ADMMass group, is respected.
+# This group may depend on local routines (excision, emask) and must be run
+# after all local routines. If we had no such a dependence, we could have
+# scheduled the integral computations simply in local mode.
+###############################################################################
 schedule GROUP ADMMass AT POSTSTEP AFTER ADMMass_InitLoopCounter WHILE ADMMass::ADMMass_LoopCounter
 {
   STORAGE:ADMMass_GFs[3]
-- 
cgit v1.2.3