...
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 USABLETempest fixes from : weights are good. row sum error 1.3e-15, conservation error: 5e-14.
Status: GOOD
ne30np4->ne512np4
Status:
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. sum error 2.2e-16. conservation error: 3.4e-1 (bilin is not conservative)
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.2e1e-67) Column sum error 1.1e9e-67
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-11max 8.5e-12. Conservation error 1.5e-11
Status: GOOD
oRRS18to6 → ne512pg2
weights are good. row sum error 1e3e-11. conservation error 1e-11
Status: GOOD
oRRS18to6 → ne1024pg2 . ( /global/project/projectdirs/acme/taylorm/mapping/map_oRRS18to6v3_to_ne1024pg2_aave.nc.BAD )
weights are bad: max 2.6
issue: ncks --chk_map row sum error 3e-11 ( so not seeing the 2.6 weight - why not?)
bad row (using 0 offset indexes) below. frac_a and frac_b are very close to 1.0. Row sum should be 3.0
i=23671483 row=16793415 col=440074 S(i)=0.01081445249957359
i=23671484 row=16793415 col=2185371 S(i)=0.01693720477026149
i=23671485 row=16793415 col=2291461 S(i)=0.06794085597402247
i=23671486 row=16793415 col=2859389 S(i)=0.219621083467022
i=23671487 row=16793415 col=2985682 S(i)=0.01041498955477845
i=23671488 row=16793415 col=3331746 S(i)=2.674271413734307
AnalyzeMap reports max rowsum = 3 (correct)
ncks --chk_map conservation error: 3.1e-11, row sum max 3.0. conservation error 4e-4
Status: NOT USABLE
Outstanding issues
...