You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of cascading interpolation everywhere, the call to retrieve_ghost_zones should only fill the boundary. For codes like Enzo which are not well-behaved, this may mean a much bigger searching process than for codes like FLASH.
Oh, I think we might be on the way to this being done for 3.3! The
optimizations do nearly this. Not sure it's worthwhile to close it, but
it's getting near.
@matthewturk I think you were interested in working on this so I've assigned it to you. I know we've had some good work on ghost zones going on (e.g. #2425), but I think this particular issue could use some TLC.
Originally reported by: Matt Turk (Bitbucket: MatthewTurk, GitHub: MatthewTurk)
Instead of cascading interpolation everywhere, the call to retrieve_ghost_zones should only fill the boundary. For codes like Enzo which are not well-behaved, this may mean a much bigger searching process than for codes like FLASH.
The text was updated successfully, but these errors were encountered: