-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parallel consistent interpolation #39
Comments
Connected to the Animate issue #71 to use subprocess to adapt, I was using subprocess to I would again do this in a separate script that I'd call from subprocess and make sure to use the same distribution parameters when I load the meshes (using |
Thanks @ddundo. We were hoping to use the new point interpolation functionality, which apparently works better in parallel. (See mesh-adaptation/animate#56). |
Thanks @jwallwork23! Could you please point me to this new interpolation? I don't think I've seen it. And do you then plan to completely drop the current projection eventually? Or will you keep both? |
It hasn't been implemented in Animate or Goalie yet but it will use point interpolation via We'll likely keep both but default to the new one if it does indeed turn out to work better in parallel. |
Closes #39. Introduces parallel-compatible mesh-to-mesh interpolation as the default transfer method --------- Co-authored-by: Joe Wallwork <22053413+jwallwork23@users.noreply.github.com>
Currently we transfer solution fields between meshes using a conservative projection method, which is difficult to get to work in parallel. It would be good if we could get consistent interpolation to work in parallel.
Parent issue: pyroteus/pyroteus#8.
The text was updated successfully, but these errors were encountered: