[Carpet] sync vs sync+restrict

[Bela Szilagyi]

Thanks! 

I can now quit making direct references to Carpet::do_prolongate ...

On Tuesday 09 May 2006 15:21, Erik Schnetter wrote:
> On May 4, 2006, at 11:09:44, Bela Szilagyi wrote:
> > Erik,
> >
> > indeed I meant prolongation rather than restriction.
> >
> > Turning off the prolongation is worth the effort in an excision
> > thorn of mine
> > that goes through the excision points layer by layer, doing up to 7
> > extra
> > syncronizations within a single MoL subiteration.  Having
> > prolongation turned
> > off (by means of the aliased function EnableProlongation) is a
> > significant
> > gain for me.
> >
> > While looking at this I realized that MoL uses the same function to
> > define
> > when should prolongation occur.  And why thinking of this came the
> > idea that
> > one could construct fully Xmas tree algorithms that would not need
> > constant
> > time-steps.
>
> I've added an aliased function QueryProlongating.  This allows you to
> find out the current state.  The idea is that you switch off
> prolongation during your excision handling, and restore the previous
> state afterwards, as in:
>
> int const old_prolongation_state = QueryProlongating ();
> EnableProlongating (0);
> /* do your stuff */
> EnableProlongating (old_prolongation_state);
>
> That should help you get more performance.
>
> -erik

-- 
Bela Szilagyi
----------------------------------------------------
Max-Planck-Institut für Gravitationsphysik
Albert-Einstein-Institut
Tel: +49 331 567 7632
Fax: +49 331 567 7649
----------------------------------------------------