...
Note2: these maps have a “mask_a,mask_b” and “frac_a,frac_b” variables. It appears “mask” is used to mask out point not used by that component model. For a global atmosphere grid, mask_b=1 for all points. For an MPAS grid, mask_a=1 for all points since the grid only contains ocean points. A POP grid is probably the only example where mask would contain both 0 and 1 values. The MPAS grid has frac_a=1 for all ocean points = all points in the grid. The mapping file value of frac_b ranges from 0..1 (we should check this) on the atmosphere grid, with coastlines given by the fractional values.
Note3: for TR FV to FV maps, the --mono options are ignored. monotone conservative maps are constructed using --in_np 1 (piecewise constant reconstruction). higher order maps (--in_np 2) are not monotone.
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
...
TR mono maps have large loss of precision. can be used for development, but not acceptable long term
MBTR 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 to ne512pg2, but both produce too large weights with ne1024pg2 (both SE->SE and FV->SE)
AnalyzeMap
request: add min/max of map file frac_a, frac_b data to output
request: check for NaNs when printing weight min/max
for non global (MPAS) source grid, prints tens of thousands of useless consistency warnings
ncremap supports “fv2fv” option:
fv2fv
(synonymsrll2rll
,accurate_monotone_nonconservative_fv2fv
),Options: ‘--in_type fv --in_np 2 --out_type fv --out_np 2 --mono3 --noconserve’
- question for Paul Ullrich is “--mono3 --noconserve” supported for FV2FV maps? Some initial results suggest this map is NOT monotone.