MPAS-Dev / MPAS

Repository for private MPAS development prior to the MPAS v6.0 release.
Other
4 stars 0 forks source link

Halo may not have full width at corners #1312

Open mark-petersen opened 7 years ago

mark-petersen commented 7 years ago

In the ocean core, there are bit-for-bit differences between one step runs with different block partitions. Adding extra halo updates fixes it, but I suspect that in a few places the halo is actually not three cells wide, as specified, but two cells wide.

mark-petersen commented 7 years ago

For a single step, the error shows up as the difference between blocks, and it occurs at corners of the block: screen shot 2017-05-04 at 8 10 53 am screen shot 2017-05-04 at 8 11 15 am screen shot 2017-05-04 at 8 12 11 am screen shot 2017-05-04 at 8 12 29 am

matthewhoffman commented 7 years ago

From Developers Guide p.18 here http://mpas-dev.github.io/ screen shot 2017-05-04 at 10 09 04 am

Cells make up the primary mesh within MPAS. Halos for cells are described below:

  • 0-Halo: All "owned" cells;

  • 1-Halo: All cells that border 0-Halo cells but are not 0-Halo cells;

  • 2-Halo: All cells that border 1-Halo cells but do not belong to a lesser halo;

  • 3-Halo: All cells that border 2-Halo cells but do not belong to a lesser halo;

Cells can have an arbitrary number of halos, in which case this incremental definition continues until the last halo layer.

Edges and Vertices have a slightly different definition and always include an additional layer.

  • 0-Halo: All "owned" edges/vertices;

  • 1-Halo: All edges/vertices that border 0-Halo cells that are not 0-Halo edges/vertices;

  • 2-Halo: All edges/vertices that border 1-Halo cells that are not 1-Halo edges/vertices;

  • 3-Halo: All edges/vertices that border 2-halo cells that are not 2-Halo edges/vertices;