Change the number of timelevels of the ahmask to match the number which is used for the metric. Setting this to three unconditionally leads to problems when running with Carpet and prolongation_order_time=1 because all GFs in Carpet are expected to have the same number of timelevels: prolongation_order_time+1.

This is not the ideal solution. That would eliminate also variables ala metric_timelevels, because they directly depend on prolongation_order_time and should not have to be set (correctly) in a parameter file. This could be done automatically.

However, this patch for now uses metric_timelevels, in order to get AHFinderDirect working quickly.


git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinAnalysis/AHFinderDirect/trunk@1554 f88db872-0e4f-0410-b76b-b9085cfa78c5

1 files changed, 1 insertions, 0 deletions

diff --git a/param.ccl b/param.ccl
index dbb29b6..ad6e3f6 100644
--- a/param.ccl
+++ b/param.ccl
@@ -20,6 +20,7 @@ USES KEYWORD rotation_axis
 # note our access is read-only
 shares: ADMBase
 USES KEYWORD metric_type
+USES CCTK_INT metric_timelevels
 
 # we need to look at SpaceMask::use_mask in order to find out about the
 # excision region