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
Is your feature request related to a problem? Please describe.
Orca meshes do not currently support MPI halos. I would like to add this support to resolve an issue in OOPS and to support more complex operations on domain decomposed orca fields in the future.
This would solve an issue caused by the OOPS observation partitioning scheme, which uses the nearest node locations to identify the owning MPI process for an observation. The atlas interpolation schemes need the cell containing the observation in order to interpolate the model data to the location. On the edge of an MPI process with halo =0, this can lead to observations on a processor but outside of the mesh.
OOPS issue solution options
Improve the OOPS observation partitioning algorithm
solves the issue at the source
hard to write a performant solution that works in general for atlas and other grids supported by oops
large project with a lot of dependent projects - any change will be difficult to make
Add halo = 1 support to orca meshes (this proposal)
adds functionality we would want anyway
solves the problem in a robust and correct way
Describe the solution you'd like
Refactor the mesh generator to allow for setting a halo > 0 at mesh generation time. This involves quite a number or ordered/connected changes across various repositories. We have a proposed solution, but it requires the following:
@matthewrmshin perhaps wait until @wdeconinck is happy to give us a new tagged release? Just in case he deploys develop somewhere and bad things happen his end? I know I have tested this change in our stack and it was fine.
Is your feature request related to a problem? Please describe.
Orca meshes do not currently support MPI halos. I would like to add this support to resolve an issue in OOPS and to support more complex operations on domain decomposed orca fields in the future.
This would solve an issue caused by the OOPS observation partitioning scheme, which uses the nearest node locations to identify the owning MPI process for an observation. The atlas interpolation schemes need the cell containing the observation in order to interpolate the model data to the location. On the edge of an MPI process with halo =0, this can lead to observations on a processor but outside of the mesh.
OOPS issue solution options
Describe the solution you'd like
Refactor the mesh generator to allow for setting a halo > 0 at mesh generation time. This involves quite a number or ordered/connected changes across various repositories. We have a proposed solution, but it requires the following:
Coordinated Changes
Organisation
UK Met Office
The text was updated successfully, but these errors were encountered: