<div dir="ltr">Hi everyone,<div><br></div><div>thanks for the answers, this clears some misconceptions on my part. The "copy" operator seems to be what I need, I'll give it a try.</div><div><br></div><div>Bye,</div><div>Federico</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-10-30 20:33 GMT+01:00 Ian Hinder <span dir="ltr"><<a href="mailto:ian.hinder@aei.mpg.de" target="_blank">ian.hinder@aei.mpg.de</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><div>On 30 Oct 2015, at 20:00, Erik Schnetter <<a href="mailto:schnetter@cct.lsu.edu" target="_blank">schnetter@cct.lsu.edu</a>> wrote:</div><br><blockquote type="cite"><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></blockquote><div><br></div><div>So really we should think of the "prolongation" tag as a more generic "how to treat this group during mesh refinement operations"? Would it make sense to introduce a new name for this tag, to avoid confusion? We would of course continue to accept the old name, for backward compatibility.</div></div><span class="HOEnZb"><font color="#888888"><br><div>
<div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><div>-- </div><div>Ian Hinder</div><div><a href="http://members.aei.mpg.de/ianhin" target="_blank">http://members.aei.mpg.de/ianhin</a></div></div></div></div></div>
</div>
<br></font></span></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><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: +49 69 798 47887</div><div>Email: guercilena[at]<a href="http://th.physik.uni-frankfurt.de" target="_blank">th.physik.uni-frankfurt.de</a></div></div></div>
</div>