Page Comparison

...

Recommended Settings for E3SM

Often map file algorithm choices dont have much of an impact on the solution, but occasionally they do.  Here is a great example showing the noise that can be generated when an aave map is used for upscaling non-flux variables:   /wiki/spaces/ECG/pages/2350776353

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.  

...

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. 

1. fluxes:  FV→FV mono
2. state variablesand vector maps:  
   1. ocn→atm: currently this map must be the same as used for fluxes (FV→FV mono)
   2. lnd↔atm and atm→ocn
      1. if source grid resolution >> target grid resolution:  "FV→FV mono"  
      2. if source grid resolution <= target grid resoluiton:  use ESMF's bilin.
         (will be replaced by TR's FV→FV intbilin when it becomes available) 

...

1. SE→FV  for fluxes:  use "SE→FV mono" 
2. SE→FV for state variablesand vector maps:  SE->FV intbilin
3. FV→SE for fluxes:  FV→SE monotr
   1. The best map is the transpose of the SE->FV map computed above:
   2. This is the most important map, as it is used to compute the domain files and defines the ocean/land mask on the atm/land grid.  
4. FV→SE for state variablesand vector maps:  
   1. ocn→atm: currently this map must be the same as used for fluxes (FV→SE monotr) 
   2. lnd→atm:   if land grid resolution >> atmosphere resolution:  "FV→SE mono". 
   3. lnd→atm:   if land grid resolution <= atmosphere resolution:   ESMF's bilin.  (replace by FV→SE intbilin if it becomes available)

...