...
TR “mono”
ne30np4 → ne256np4
Tempest 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 sum error 2.2e-16. conservation error: 3.4e-1 (bilin is not conservative)
mapping file frac_a=0 (BUG?), but frac_b=1
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.
MPAS → np4 grids
The TR improvements suggest we should take another look at “mono” maps for MPAS/EAM coupling:
TR “mono”
oRRS18to6 → ne256np4
oRRS18to6 → ne512np4
oRRS18to6 → ne1024np4
MPAS → pg2 grids
We expect SCREAM will ultimately be running on the ne1024pg2 “phys grid”. To create these compsets, we first need to create a domain file which needs the monotone map from the MPAS ocean grid to the pg2 grid.
...