Open bekozi opened 5 years ago
Note, this issue is important for CTSM... https://github.com/ESCOMP/ctsm/issues/806
Starting to look into this and plan to collect requirements here:
src_index_remap
.The approach no longer needs the remapping in ocgis since we can set the arbitrary sequence indices directly on the esmf grid through python. Ocgis will just detect the indices on the source grid and use those when calling esmf weight generation.
Arbitrary sequence indices are only implemented for Grid
objects in ESMPy. The Mesh
global sequence index tracking will take some tweaking to ESMF IO routines. For grids, the global index tracking is working in parallel. I'll update with Mesh
progress as it moves forward.
We finally identified the right approach for this that is sustainable moving forward. When the MOAB backend is enabled for the ESMF Mesh
(required for ESMF version 8.1 forward), we can modify the sequence indices of Mesh
after it is created. This way we don't have to mess around with quasi-IO standards when modifying the indexing used by the regridding for meshes. @rokuingh is working on changing the mesh indices using ESMF-MOAB.
When a spatial subset is used with a chunked regridding operation, the mapping to global indices is lost. These indices should be tracked and used during weight file reconstruction.