Versions Compared

Old Version 11

changes.mady.by.user Mark Taylor

Saved on

compared with

New Version 12

changes.mady.by.user Mark Taylor

Saved on

Key

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

...

  • TR “mono”

    • ne30np4 → ne256np4

      • NaNs in weights.

      • issue: ncks --chk_map and AnalyzeMap ignore NaNs when computing weight min/max.

      • issue: AnalyzeMap ignores NaNs when computing row sum

      • Status: NOT USABLE

    • ne30np4->ne512np4

      • NaNs in weights.

      • Status: NOT USABLE

  • MBTR “mono”

    • ne30np4->ne256np4

    • --monotonic 1: mapping weights have NaNs

    • --monotonic 3 --noconserve (“intbilin” option) weights are bad, max = 2.5

    • Status: NOT USABLE

  • ESMF “bilin”

    • ne30np4->ne256np4

      • weights between [0,1]. row sums are perfect. mapping file frac_a=0 (BUG?), but frac_b=1

      • ncks --chk_map col sums “frac_a” min/max=0. (perhaps because file’s frac_a=0?)

      • Status: GOOD

    • ne120np4->ne1024np4

      • 10M out of 120M weights are bad, >> 1.0. max row sum = 5.0

      • Status: NOT USABLE

  • ESMF “aave”

    1. We dont consider these maps. We are trying to move away from these maps since they require the “dual grid”, which is difficult to produce and unnatural for GLL grids.

...