Page Comparison

...

All mapping files should be tested as described in the "Testing and Validating Mapping Files" section below.   This testing is necessary, but not sufficient to ensure good results.  

E3SMv3 with pg2

Similar to E3SMv2 with pg2 but respecting the conventions in Mapping file algorithms and naming convention and using TempestRemap (or mbtempest) for bilinear maps.

1. fluxes:  FV→FV aave for nearly all cases
2. state and vector maps:  
   1. ocn→atm: currently this map must be the same as used for fluxes (FV→FV aave)
      1. This restriction is because the range of the state and vector maps must match the range of the flux map.  
   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):  TR 2nd-order with non-linear correction ("nlmap").   Needed for atm→lnd in trigrid.
   3. riv → ocn
      1. continue to use custom maps generated by E3SM/cime/tools/mapping/gen_mapping_files/runoff_to_ocn

E3SMv2 with pg2

ATM FV grids with physics on the 2x2 physgrid (i.e. pg2) coupled to FV ocean and FV land. E3SMv2 will still use the spectral element dynamical core on the GLL grid, but the coupling between component always happens between the physics columns, which are now on a FV grid. 

...