Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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. Usage with ncremap:

      • ncremap -s grd_src.nc -g grd_dst.nc -a ncoaave -m map_grida_to_gridb_ncoaave.YYYYMMDD.nc

      • ncremap -s grd_src.nc -g grd_dst.nc -a esmfaave -m map_grida_to_gridb_ncoaaveesmfaave.YYYYMMDD.nc

      • ncremap -s grd_src.nc -g grd_dst.nc -a traave -m map_grida_to_gridb_traave.YYYYMMDD.nc

  • bilin: bilinear interpolation

    • can be produced by: ESMF, TR/MBTR

      • ESMF: ESMF_RegridWeightGen -s srcmesh.nc -d dstmesh.nc -w mapfile.nc --method bilinear --extrap_method nearestidavg

      • TempestRemap:

        1. GenerateOfflineMap --a srcmesh.nc --b dstmesh.nc --out ov_mesh.nc --allow_no_overlap

        2. GenerateOfflineMap --in_mesh srcmesh.nc --out_mesh dstmesh.nc --ov_mesh ov_mesh.nc --in_type fv --out_type fv --method bilin --out_map mapfile.nc

      • mbtempest: mbtempest --type 5 --load srcmesh.nc --load dstmesh.nc --intx intersection_mesh.h5m --weights --method fv --method fv --order 1 --order 1 --fvmethod bilin --file mapfile.nc

    • 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 barycentric (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: TR software may have some issues when source grid has holes.

    • examples: trintbilin, mbtrintbilin

    • trintbilin: Pass --method intbilin option to TempestRemap’s GenerateOfflineMap

    • mbtrintbilin: Pass --fvmethod intbilin option to mbtempest

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

  • nn: nearest neighbor

    • used with river runnoff maps

...

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

SE to/from FV Algorithms: (no longer used by E3SM, but used for some analysis tasks)

...


_aave.nc:        ESMF conservative/monotone "area averaged" maps. NOW: esmfaave
_bilin.nc:       ESMF bilinear NOW: esmfbilin
_mono.nc       TempestRemap conservative, monotone map NOW: “mono” is reserved for when the source is an SE grid. When its FV (as in ne30pg), use traave.
_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) 

...