...
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 with new --correct_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
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-03
oRRS18to6 → ne1024pg2: status: GOOD
15.5h on Anvil, using 20GB
weights: good. row sum error: 4e-16. conservation error: 1e15
MBTR “mono”. Status: NOT USABLE
oRRS18to6 → ne256pg2
Weights are good, but 316 MPAS grid points have weight=0. This is incorrect and corrupts other diagnostics.
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
weights are good. row sum error 3e-11. conservation error 1e-11
vortex: l2, linf: 1.7866e-04 2.2985e-03
oRRS18to6 → ne1024pg2. Status: NOT USABLE
35min on Cori Haswell node
( /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
same issue with ESMF v8.
...