<div dir="ltr">none: Do nothing during synchronization, prolongation, or restriction; the respective grid points remain untouched, and if not otherwise defined, remain undefined. This is<div>commonly used e.g. for integer values that are calculated or determined pointwise.</div><div><br><div>sync: Synchronize only, do nothing for prolongation or restriction. This is similarly useful e.g. for integer data.</div></div><div><br></div><div>restrict: Only synchronize and restrict from coarser to finer grids, do nothing during prolongation. For vertex centred data where restriction is an injection, this can also still be used for integer values. Otherwise this may be useful for data that are not needed in prolongation regions, but where the coarse grid has data worse than the fine grid, e.g. for constraints.</div><div><br></div><div>copy: Copy from the nearest neighbour instead of interpolating. This can likewise be used for integer data.</div><div><br></div><div>All other settings define actual prolongation operators.</div><div><br></div><div>-erik</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Oct 26, 2015 at 11:51 AM, Federico Guercilena <span dir="ltr"><<a href="mailto:guercilena@th.physik.uni-frankfurt.de" target="_blank">guercilena@th.physik.uni-frankfurt.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hello,</div><div><br></div><div>could anyone tell me a few details regarding the Carpet prolongation operators? It appears there's no real documentation about them. Looking at Carpet source code I can see these operators are available:</div><div><br></div><div><div><div>none<br></div><div>sync</div><div>restrict</div><div>copy</div><div>Lagrange<br></div><div>ENO<br></div><div>ENOVOL<br></div><div>WENO<br></div><div>TVD<br></div><div>Lagrange_monotone<br></div><div>STAGGER011<br></div><div>STAGGER101<br></div><div>STAGGER110<br></div><div>STAGGER111</div></div><div><br></div><div>The "polynomial" ones (Lagrange, ENO, etc) appear to be self explanatory, more or less. I'm particularly interested in the exact behaviour of "none", "sync" and "copy". "none" and "sync" are the same thing apparently. I find the "restrict" operator very confusing, since these are supposed to take care of prolongation.</div><div><br></div><div>I'm asking because in a thorn I'm working on, a certain GF has prolongation set to "None". This resulted in buffer zones on finer grids not to be initialized (full of NaNs) when switching on mesh refinement. Although I think I found a workaround, I'd like to take care of this by using some already provided mechanism, if available.</div><div><br></div><div>Thank you very much,</div><div>Federico Guercilena</div><span class="HOEnZb"><font color="#888888"><div><br></div>-- <br><div><div dir="ltr"><div>Federico Guercilena</div><div>Institut für Theoretische Physik</div><div>Johann Wolfgang Goethe-Universität</div><div>Max-von-Laue-Str. 1</div><div>60438 Frankfurt am Main, Germany</div><div>Telephone: <a href="tel:%2B49%2069%20798%2047887" value="+496979847887" target="_blank">+49 69 798 47887</a></div><div>Email: guercilena[at]<a href="http://th.physik.uni-frankfurt.de" target="_blank">th.physik.uni-frankfurt.de</a></div></div></div></font></span></div></div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@einsteintoolkit.org">Users@einsteintoolkit.org</a><br>
<a href="http://lists.einsteintoolkit.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.einsteintoolkit.org/mailman/listinfo/users</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Erik Schnetter <<a href="mailto:schnetter@cct.lsu.edu" target="_blank">schnetter@cct.lsu.edu</a>><br><a href="http://www.perimeterinstitute.ca/personal/eschnetter/" target="_blank">http://www.perimeterinstitute.ca/personal/eschnetter/</a></div>
</div>