Page Comparison

...

1. fluxes:  
   1. if source grid resolution >> target grid resolution:   FV→FV aave 
   2. if source grid resolution <= target grid resolution:   V3 is considering adopting FV2+CAAS 
2. state and vector maps:  
   1. 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.  
      1. This usually means we must use the same map as used for fluxes.    
      2. 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?).        
   2. lnd↔atm and atm→ocn
      1. if source grid resolution >> target grid resolution (fine-to-coarse):  "FV→FV aave"  
      2. if source grid resolution <= target grid resolution (nearly equivalent resolutions):   Use TR bilin
      3. if source grid resolution << target grid resolution (coarse-to-fine):  FV2+CAAS.   Needed for atm→lnd in trigrid.
      4. Why do we still recommend aave or bilin above?  intbilin or FV2+CAAS approach should be better in both cases.  
   3. riv → ocn
      1. continue to use custom maps generated by E3SM/cime/tools/mapping/gen_mapping_files/runoff_to_ocn

...