#2086: Perform only spatial prolongation when using a single timelevel and tag 'prolongation="copy"' -------------------------------------------------------+-------------------- Reporter: miguel.zilhao.nogueira@… | Owner: eschnett Type: defect | Status: new Priority: unset | Milestone: Component: Carpet | Version: development version Keywords: | -------------------------------------------------------+-------------------- Sometimes it is useful to set a grid function that does not evolve at all. However, using a single timelevel and tag 'prolongation="copy"' results in a Carpet assertion failure.
This is fixed in the following commit d13a6e245a3d7d2b575094fd0def540d510a166c, as discussed in the following thread: http://lists.einsteintoolkit.org/pipermail/users/2017-October/005835.html
Could this be merged to master?
#2086: Perform only spatial prolongation when using a single timelevel and tag 'prolongation="copy"' --------------------------------------------------------+------------------- Reporter: miguel.zilhao.nogueira@… | Owner: eschnett Type: defect | Status: new Priority: unset | Milestone: Component: Carpet | Version: development version Resolution: | Keywords: --------------------------------------------------------+-------------------
Comment (by eschnett):
{{{op_copy}}} was designed to copy data from coarse to the fine level without any kind of interpolation. This would work with all data types, including integers. I don't recall whether its meaning has changed in the mean time. As I recently realized, {{{op_copy}}} does not work with cell- centred refinement since there is then no nearest point from which to copy.
We can introduce a new prolongation operator and/or introduce a way to set the desired time prolongation order per grid function group.
trac@lists.einsteintoolkit.org