aboutsummaryrefslogtreecommitdiff
path: root/Carpet/Carpet/src/Restrict.cc
diff options
context:
space:
mode:
authorErik Schnetter <schnetter@gmail.com>2013-05-26 16:50:34 -0400
committerErik Schnetter <schnetter@gmail.com>2013-05-26 16:50:34 -0400
commit4acaa0d0d3e59d6e618815515871f1f1115a6789 (patch)
tree1db95dd736dc25e23b44e98ae671c0f463041eca /Carpet/Carpet/src/Restrict.cc
parent3f3b57db6d8238c2b94502e278d71ffbc186d3d8 (diff)
Carpet: Disable automatic synchronisation after restriction
Restricted grid functions have boundary conditions applied anyway (if used correctly), which involves synchronisation (if done correctly). An explicit synchronisation is thus only overhead.
Diffstat (limited to 'Carpet/Carpet/src/Restrict.cc')
-rw-r--r--Carpet/Carpet/src/Restrict.cc5
1 files changed, 5 insertions, 0 deletions
diff --git a/Carpet/Carpet/src/Restrict.cc b/Carpet/Carpet/src/Restrict.cc
index a3b6b3439..6dc040c23 100644
--- a/Carpet/Carpet/src/Restrict.cc
+++ b/Carpet/Carpet/src/Restrict.cc
@@ -70,12 +70,17 @@ namespace Carpet {
}
// Synchronise
+ // TODO: Why? Restricted grid functions need to have boundary
+ // conditions applied in postrestrict anyway, so this should not
+ // be necessary.
+#if 0
{
static Timer timer ("RestrictSync");
timer.start();
SyncGroups (cctkGH, groups);
timer.stop();
}
+#endif
}