#1499: Error in synchronisation after restriction ---------------------+------------------------------------------------------ Reporter: hinder | Owner: eschnett Type: defect | Status: closed Priority: major | Milestone: ET_2014_05 Component: Carpet | Version: development version Resolution: fixed | Keywords: ---------------------+------------------------------------------------------
Comment (by hinder):
Do those tests have 3 refinement levels? I wasn't able to reproduce the problem with 2. Since we are now syncing when using higher order restriction, whereas before we weren't, ideally the existing tests should now be failing as the data is different (and correct). This suggests the original tests didn't trigger this problem (e.g. only 2 levels) or the output didn't catch the problem region (the finest grid region of the coarse grid, in a 3-level simulation). It would be good to modify the test I just added (test_restrict_sync) to use higher order restriction, and check that it fails before these fixes and passes afterwards. Do you want to do that?