Versions Compared

Key

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

...

  • TR “mono”

    • ne256np4 → oRRS18to6 ( with TR from )

      • weights: good. row sum error: 1e-15 . Conservation error: 4e-14

    • ne512np4 → oRRS18to6

      • ~4h to compute overlap mesh

      • ..EXCEPTION (src/LinearRemapSE0.cpp, Line 1016) Target grid must be a subset of source grid:

        Input mesh area (7.245674993333319e-06) Target area (2.898288183419045e-05)

    • ne1024np4 → oRRS18to6

MPAS → pg2 grids

...

  • TR “mono”

    • oRRS18to6 → ne256pg2 (TR from with --correct_ares)

      • takes about 7h to produce (single processor)

      • Weights are good. Row sums error: 7e-16. Conservation error 7e-16

      • vortex test field l2/max error: 3.6145e-05 4.3881e-04

      • Status: GOOD

    • oRRS18to6 → ne512pg2: COMPUTING…

      • ~9h to compute overlap map

      • weights: good. row sum error: 7e-16. Conservation error 7e-16

      • vortex:     l2, linf: 1.7867e-04 2.2985e-03

    • oRRS18to6 → ne1024pg2: how long on a single core?

  • MBTR “mono”

    • oRRS18to6 → ne256pg2

    • Weights are good, but 316 MPAS grid points have weight=0. This is incorrect and corrupts other diagnostics.

    • Status: NOT USABLE

  • ESMF “aave”

    • oRRS18to6 → ne256pg2

      • weights are good. row sum max 8.5e-12. Conservation error 1.5e-11

      • vortex test field l2/max error: 3.6144e-05 4.3881e-04

      • Status: GOOD

    • oRRS18to6 → ne512pg2

      • weights are good. row sum error 3e-11. conservation error 1e-11

      • vortex:     l2, linf: 1.7866e-04 2.2985e-03

      • Status: GOOD

  • oRRS18to6 → ne1024pg2 . ( /global/project/projectdirs/acme/taylorm/mapping/map_oRRS18to6v3_to_ne1024pg2_aave.nc.BAD )

    • weights are bad: max 2.6, row sum max 3.0. conservation error 4e-4

    • Status: NOT USABLE

Outstanding issues

  • TR mono maps have large loss of precision. can be used for development, but not acceptable long term

  • MBTR FV->FV error - missing source points. It appears MBTR maps have a similar loss of precision as TR maps, but this could be corrupted du to the missing source points.

  • MBTR SE->SE: montone weights are bad, either NaN or >1

  • ESMF “aave” and “bilin” maps are good up to ne512pg2, but both produce too large weights with ne1024pg2 (both SE->SE and FV->SE)

  • AnalyzeMap

    • request: add min/max of map file frac_a, frac_b data to output

    • request: check for NaNs when printing weight min/max

    • for non global (MPAS) source grid, prints tens of thousands of useless consistency warnings

...