The internal model of the Parcels XGrid class doesn't have the concept of face connectivity, and assumes that data is defined along X, Y, Z, T dimensions (where X, Y, Z correspond to lon and lat). There isn't a "tile" dimension.
At the moment its very unclear how we could support models like ECCO (perhaps via unstructured grids? Perhaps via another custom grid class? perhaps (IMO, this option is the least viable) by expanding the XGrid class in a reasonable way?).
Face connectivity is also something that we need to consider when it comes to position searching (which also applies to tri-polar grids).
Let's use this issue to house discussion. Note that this is a low priority for Parcels v4.0 .
I don't think it is something that we worry about at this point in the code for now. I don't think we should support ECCO for now as face connectivity is not something we deal with at the moment. Perhaps its something we can discuss with xgcm people since they also deal with this face connectivity problem
Originally posted by @VeckoTheGecko in #2091 (comment)
The internal model of the Parcels XGrid class doesn't have the concept of face connectivity, and assumes that data is defined along X, Y, Z, T dimensions (where X, Y, Z correspond to lon and lat). There isn't a "tile" dimension.
At the moment its very unclear how we could support models like ECCO (perhaps via unstructured grids? Perhaps via another custom grid class? perhaps (IMO, this option is the least viable) by expanding the XGrid class in a reasonable way?).
Face connectivity is also something that we need to consider when it comes to position searching (which also applies to tri-polar grids).
Let's use this issue to house discussion. Note that this is a low priority for Parcels v4.0 .
I don't think it is something that we worry about at this point in the code for now. I don't think we should support ECCO for now as face connectivity is not something we deal with at the moment. Perhaps its something we can discuss with xgcm people since they also deal with this face connectivity problem
Originally posted by @VeckoTheGecko in #2091 (comment)