[ET Trac] [Einstein Toolkit] #380: The number of timelevels for the AHFinder mask needs to be set to something intelligent. (was: AHFinderDirect failure with qc0-mclachlan.par)

Einstein Toolkit trac-noreply at einsteintoolkit.org
Tue Apr 19 11:34:28 CDT 2011


#380: The number of timelevels for the AHFinder mask needs to be set to something
intelligent.
---------------------+------------------------------------------------------
  Reporter:  hinder  |       Owner:            
      Type:  defect  |      Status:  new       
  Priority:  minor   |   Milestone:  ET_2011_11
 Component:  Other   |     Version:            
Resolution:          |    Keywords:            
---------------------+------------------------------------------------------
Changes (by knarf):

  * priority:  major => minor
  * milestone:  ET_2011_05 => ET_2011_11


Old description:

> Trying to run the par/qc0-mclachlan.par in the ET trunk gives the
> following error:
>
> INFO (AHFinderDirect): proc 0: searching for horizons 1,5/6
> WARNING level 0 in thorn CarpetInterp processor 0 host
> kop193.datura.admin
>   (line 1683 of
> /home/ianhin/Cactus/etrelease/arrangements/Carpet/CarpetInterp/src/interp.cc):
>   -> Grid function "AHFINDERDIRECT::ahmask" has only 1 active time levels
> on refinement level 1; this is not en
> ough for time interpolation
>
> See also #373, which might be related.

New description:

 The number of timelevels for AHFinderdirect::ahmask has to be set to
 something intelligent. Setting it to some fixed number doesn't work,
 because the number of timelevels for a given time-integrator might be
 different and Carpet chokes in that situation. At the moment it's set to
 how-many timelevels ADMBase::metric has, but that's also not good because
 that might be 1, while ahmask should have more. We cannot couple
 AHFinderDirect to any evolution thorn or Carpet as well. We might have to
 introduce a new parameter, but I would like to avoid this if somehow
 possible (which is why I coupled it to the metric in the first place,
 hoping this would be ok, which is apparently not really the case).

--

Comment:

 We now set the number of timelevels for the metric to three, which solves
 the problem for now. I change the description to match the problem which
 is not really solved.

-- 
Ticket URL: <https://trac.einsteintoolkit.org/ticket/380#comment:8>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit


More information about the Trac mailing list