...
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->ne512np4
Status: GOOD
ne120np4->ne1024np4
10M out of 120M weights are bad, >> 1.0. max row sum = 5.0
Status: NOT USABLE
ESMF “aave”
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.
...
TR “mono”
oRRS18to6 → ne256pg2
takes about 7h to produce (single processor)
Weights are good. Row sums are bad (1.2e-6) Column sum error 1.1e-6
Status: usable for development. NOT USABLE FOR PRODUCTION
oRRS18to6 → ne1024pg2: too expensive/too much memory. need MBTR to compute in parallel.
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 error 1e-11. Conservation error 1.5e-11
Status: GOOD
oRRS18to6 → ne512pg2
weights are good. row sum error 1e-11. conservation error 1e-11
Status: GOOD
oRRS18to6 → ne1024pg2
weights are bad: max 2.6
issue: ncks --chk_map row sum error 3e-11 ( so not seeing the 2.6 weight - it’s probably in a region with frac_a or frac_b << 1)
AnalyzeMap reports rowsum = 3 (consistent with 2.6 weight)
ncks --chk_map conservation error: 3.1e-11
AnalyzeMap:
Status: NOT USABLE
...
TR mono maps have large loss of precision. can be used for development, but not acceptable long term
MBTR maps have bugs (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 ot to ne512pg2, but both produce too large weights with ne1024pg2 (both SE->SE and FV->SE)
AnalyzeMap
for MPAS->SE map, row sum calculation reports large errors, for points where frac_b<<1. is this due to lack of normalize row sums with frac_b?
request: add min/max of frac_a, frac_b to output
request: check for NaNs when printing weight min/max
ncks --chk_map
request: add min/max of frac_a, frac_b to output
request: check of for NaNs when printing min/max
for MPAS->atm grid with bad weights (> 1.0) not detected in row sums. Is this due to normalzation normalization of row sums by frac_b?