Page Comparison

...

Note3: for TR FV to FV maps, the --mono options are ignored. monotone conservative maps are constructed using --in_np 1 (piecewise constant reconstruction). higher order maps (--in_np 2) are not monotone.

• TR “mono”ncremap build in FV to FV map file generator

  • oRRS18to6 → ne256pg2 status: GOOD

    • ~3min with 4 threads on Cori frontend node

    • Weights are good. row sum and conservation error: 6e-13

  • oRRS18to6 → ne1024pg2

    • ~40 min on Compy with 4 threads

• TR “mono” . (TR from TR from 17 Jan 2020 with new --correct_

  ares

  areas option)

  • oRRS18to6 → ne256pg2 status: GOOD

    • 2.5h on Anvil (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: status GOOD

    • ~9h to compute overlap map

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

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

  • oRRS18to6 → ne1024pg2: status: GOOD

    • 15.5h on Anvil, using 20GB

    • weights: good. row sum error: 4e-16. conservation error: 1e15

• MBTR “mono”. Status:

  GOOD

  NOT USABLE

  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. Status: GOOD

    • 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

  • oRRS18to6 → ne512pg2. 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. Status: NOT USABLE

    • ( /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-4Status: NOT USABLE

Outstanding issues

• 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

...