...
- fluxes:
- if source grid resolution >> target grid resolution: FV→FV aave
- if source grid resolution <= target grid resolution: V3 is considering adopting FV2+CAAS
- state and vector maps:
- ocn→atm: currently this map must be the same as used for fluxes (FV→FV aave)This restriction is because the range of the state and vector maps must match the range of the flux map.The state map's non-zero pattern must be a superset of the ocn→atm flux map.
- This usually means we must use the same map as used for fluxes.
- The FV2+CAAS approach should be used approach (with aave basemap) is the best choice (not sure if this was tested in time for V3?).
- lnd↔atm and atm→ocn
- if source grid resolution >> target grid resolution (fine-to-coarse): "FV→FV aave"
- if source grid resolution <= target grid resolution (nearly equivalent resolutions): Use TR bilin
- if source grid resolution << target grid resolution (coarse-to-fine): FV2+CAAS. Needed for atm→lnd in trigrid.
- Why do we still recommend aave or bilin above? intbilin or FV2+CAAS approach should be better in both cases.
- riv → ocn
- continue to use custom maps generated by E3SM/cime/tools/mapping/gen_mapping_files/runoff_to_ocn
- ocn→atm: currently this map must be the same as used for fluxes (FV→FV aave)This restriction is because the range of the state and vector maps must match the range of the flux map.The state map's non-zero pattern must be a superset of the ocn→atm flux map.
...