Page Comparison

...

• aave: Maps which compute a common refinement (intersection) mesh and then integrate a piecewise-constant reconstruction.

  • can be produced by: ESMF, NCO and TR/MBTR

  • pros: conservative, montonone, cell averaging good for fine-to-coarse maps.

  • cons: 1st order accurate, not suitable for coarse-to-fine maps (blocky results)

  • examples: esmfaave, ncoaave, traave

• bilin: bilinear interpolation

  • can be produced by: ESMF, TR/MBTR

  • pros: monotone, 2nd order accurate

  • cons: non-conservative. not suitable for fine-to-coarse maps (aliasing errors)

  • examples: esmfbilin, trbilin

• patch: patch based algorithm (L2 projection?).

  • can be produced by: ESMF only

  • pros: accurate. good for coarse-to-fine maps. not sure how it performance on fine-to-coarse maps.

  • cons: can have small non-monotone weights

  • examples: esmfpatch

• intbilin: Integrated bilinear or trilinear (TR/MBTR only)

  • can be produced by: TR, MBTR only.

  • pros: monotone, 2nd order, good for fine-to-coarse and coarse-to-fine maps.

  • cons: may have some issues when source grid has holes.

  • examples: trintbilin, mbtrintbilin

  What’s the new map used for nonlinear tweaks needed for trigrid? I think TR’s “np2” - 2nd order FV?

• fv2 (or fvnp2): 2nd order FV reconstruction, cell integrated on target grid (TR/MBTR only)

  • pros: 2nd order, conservative

  • cons: not monotone

  • Made monotone via E3SM v3 coupler’s nonlinear fixer. Used in E3SM trigrid configurations as a flux map in order to avoid blockyness caused by aave maps.

  • examples: trfv2

• nn: nearest neighbor

  • used with river runnoff maps

Examples:

Suffix = esmfaave, esmfbilin, ncoaave, trmono, trmonotrn, trintbilin, trhighorder, mbtrmono, ...

...