Proposed naming convention for E3SM V2 and newer compsets:
Suffix = ToolAlgorithm
where Tool = esmf,nco,tr (soon to include mbtr for MOAB-Tempest).
Algorithm:
aave: Maps which compute a common refinement (intersection) mesh and then integrate a piecewise-constant reconstruction. Conseravtive and monotone.
bilin: ESMF’s bilinear interpolation
mono: For spectral element (SE) grids, where the spectral element basis functions are replaced with a montone bases.
intbilin: Integrated bilinear. For finite element grids, the shape functions are replaced by a piecewise linear shape functions which are then integrated using a common refinement mesh
highorder:
{algorithm}trn: For any map from grid a to grid b, one can compute an area weighted transpose map from grid b to grad a. In general, the tranpose map will not preserve the properties of the original map. However, the transpose of a conservative map will be conservative. The transpose of a monotone conservative map will be monotone and conservative.
thus, currently:
Suffix = esmfaave, esmfbilin, ncoaave, trmono, trmonotrn, trintbilin,
trhighorder, mbtrmono, ...
Historical usage:
_aave.nc: ESMF conservative/monotone "area averaged" maps
_bilin.nc: ESMF bilinear
_mono.nc TempestRemap conservative, monotone map
_highorder.nc TempestRemap high-order, conservative, non-monotone ( several TR options in this category )
_intbilin.nc TempestRemap integrated bilinear: monotone, non-conservative
_monotr.nc TempestRemap transpose of a mono map.
_highordertr.nc TempestRemap transpose of a highorder map. (not recommended)
_conserve.nc. Used for a short time for TR conservative, high-order, non-monotone maps. Confusing since "conserve" implies it's a replacement for an "aave" type map, when really that type of map is a replacement for "bilin".