#594: Order of restriction and calls to POSTRESTRICTINITIAL in Initial timebin ---------------------+------------------------------------------------------ Reporter: rhaas | Owner: eschnett Type: defect | Status: review Priority: minor | Milestone: Component: Carpet | Version: Resolution: | Keywords: ---------------------+------------------------------------------------------
Comment (by eschnett):
The do_every logic in Evolve.cc is supposed to prevent this. Restriction only occurs when times are aligned. This logic is not necessary in Initialise.cc.
init_3_timelevels initialises only one timelevel, then evolves forward and backward in time to fill the other two. I don't recall whether restriction occurs there, but if so, it is not via the routine CallRestrict in Initialise.cc.
I have not checked the patch in detail, but it seems correct. Please apply.