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