[Carpet] sync vs sync+restrict

[Erik Schnetter]

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

-- 
Erik Schnetter <schnetter at cct.lsu.edu>

My email is as private as my paper mail.  I therefore support encrypting
and signing email messages.  Get my PGP key from www.keyserver.net.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : /archives/developers/attachments/20060509/96ba3b72/attachment.pgp