Joe Schoonover

I think this case will need barycentric coordinates calculated using cartesian coordinates. A colinear face in lat-lon space violates the assumption of having a convex polygon required for the barycentric...

@philipc2 and @aaronzedwick - I have some time to knock this out in the next couple weeks. Essentially, this will add an option to use cartesian coordinates and a 3-D...

Hey @aaronzedwick - I've pushed up a branch that adds your reproducer as a test and provides functions for computing barycentric coordinates using cartesian points. Before I get too far...

It occurs to me that, even if a point is not in the same plane as the polygon, we can still end up with "reasonable" barycentric coordinates ( the sum...

I don't think it's a corner case. Working with 2-d surfaces in 3-d space requires both checks (valid barycentric coordinates and point-in-plane). When using `_barycentric_coordinates_cartesian` in the `SpatialHash.query`, we definitely...

@michaeldenes - fields on structured grids are brought in consistent with the way things are done in [xgcm](https://xgcm.readthedocs.io/en/latest/). The plan is to have some built in interpolators for existing GCMs....

Currently running into a build issue here with the build in the docker container during the CMake stage ``` found MPI_C: /opt/views/view/lib/libmpi.so (found version "3.1") Could NOT find MPI_Fortran (missing:...

Clean build today and everything is working for the x86_64 image. Moving on to the ROCm images

Since this `mesh_type` attribute is really used to determine if unit conversions should be applied, I'd argue that it'd be better to just attach a "unit converter" to a Field...

I think this is a good way to clean things up. Though this may be implied already, want to make sure to point out the `VectorField` could also have an...