Modify

Opened 8 months ago

Last modified 8 months ago

#2086 new defect

Perform only spatial prolongation when using a single timelevel and tag 'prolongation="copy"'

Reported by: miguel.zilhao.nogueira@… Owned by: Erik Schnetter
Priority: unset Milestone:
Component: Carpet Version: development version
Keywords: Cc: Ian Hinder

Description

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?

Attachments (0)

Change History (1)

comment:1 Changed 8 months ago by Erik Schnetter

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.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The owner will remain Erik Schnetter.
Next status will be 'review'.
as The resolution will be set.
to The owner will be changed from Erik Schnetter to the specified user.
Next status will be 'confirmed'.
The owner will be changed from Erik Schnetter to anonymous.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.