Open pp-mo opened 2 years ago
In order to maintain a backlog of relevant issues, we automatically label them as stale after 500 days of inactivity.
If this issue is still important to you, then please comment on this issue and the stale label will be removed.
Otherwise this issue will be automatically closed in 28 days time.
See #4751 and #5991
The definitive metadata of a MeshCoord is just
mesh
,location
+axis
.These can be leniently compared with another one, e.g. to fetch the matching coord from a cube on a different mesh : For example...
However, a MeshCoord can be "reduced" to an equivalent AuxCoord (i.e. with same names, units, points + bounds). This happens automatically when a cube is sub-indexed, e.g. "meshcube[..., 2]" or just "meshcube[..., 0:]". However, the AuxCoord can never "compare with" the original, since the metadata structure is too different. Hence, code analagous to the above won't work...
I.E. you cannot find the "equivalent" coord in this way, when one is a MeshCoord and the other a 'normal' Coord. However, that does work for a "normal" cube, including finding matching coords of a different type i.e. DimCoord <-> AuxCoord.
This is likely to cause problems in some generic operations, e.g. regridding.