Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • SE→FV mono. (conservative, monotone, 1st order)
    • ./GenerateOfflineMap --in_mesh $atmgrid --out_mesh $ocngrid --ov_mesh overlap_mesh.g --in_type cgll --in_np 4  --out_type fv  --mono --correct_areas --out_map map_atm2ocn_mono.nc
  • SE→FV intbilin (nonconservative, monotone, higher order)
    • ./GenerateOfflineMap --in_mesh $atmgrid --out_mesh $ocngrid --ov_mesh overlap_mesh.g --in_type cgll --in_np 4  --out_type fv --mono3 --noconserve --correct_areas --out_map map_atm2ocn_intbilin.nc
  • SE→FV highorder. (conservative, nonmonotone)
    • ./GenerateOfflineMap --in_mesh $atmgrid --out_mesh $ocngrid --ov_mesh overlap_mesh.g --in_type cgll --in_np 4  --out_type fv --correct_areas --out_map map_atm2ocn_highorder.nc
  • FV→SE monotr. (conservative, monotone, 1st order)
  • FV→SE highorder. (conservative, non-monotone)
    • ./GenerateOfflineMap --in_mesh $ocngrid --out_mesh $atmgrid --ov_mesh overlap_mesh.g --in_type fv --in_np 2 --out_type cgll --out_np 4  --volumetric --out_map map_ocn2atm_highorder.nc
    • Does these maps need "–correct_areas" ?
  • FV→SE mono. (conservative, monotone, 1st order)
    • ./GenerateOfflineMap --in_mesh $ocngrid --out_mesh $atmgrid --ov_mesh overlap_mesh.g --in_type fv --in_np 1 --out_type cgll --out_np 4 - -volumetric --out_map map_ocn2atm_mono.nc
    • Does these maps need "–correct_areas" ?
  • FV→SE intbilintr  (nonconservative, nonmonotone, higher order)
  • FV→FV "aave" (conservative, monotone, 1st order)
    • The classic cell integrated piecewise constant map.  Equivalent to the ESMF "aave" map and NCO's built in map.  
    • ./GenerateOfflineMap --in_mesh $ocngrid --out_mesh $atmgrid --ov_mesh overlap_mesh.g --in_type fv --in_np 1 --out_type fv --out_np 1 -correct_areas  --out_map map_ocn2atm_mono.nc
  • FV→FV highorder. (conservative, non-monotone, high order)
    • ./GenerateOfflineMap --in_mesh $atmgrid --out_mesh $ocngrid --ov_mesh overlap_mesh.g  --in_np 2 --in_type fv  --out_type fv  --out_np 1 -correct_areas --out_map map_atm2ocn_highorder.nc
    • --in_np 2 means all the nearest neighbor cells will be used for a higher order reconstruction of the source data, which will then be integrated over the target cell.  Unlike the SE case, no mass matrix is used for an FV target grid, and thus --out_np is ignored (and will always be 1 internally).  

...

  1. SE → FV  for fluxes:  use "mono" 
  2. SE → FV for state variables:  "highorder". ). not recommended.  
  3. SE → FV for state variables:  intbilin
  4. FV → SE for fluxes:  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.  
  5. FV → SE for state variables and velocity:  highorder.   not recommended.  
    1. Tests with ocean120→NE30, analytic fields, show this map is more accurate than the transpose map
    FV → SE mono.  
    1. This is also a good monotone/conservative map for fluxes, but not quite as accurate (in analytic tests) as the transpose map recommended above
  6. FV → SE for state variables
    1. ocn→atm: currently this map must be the same as used for fluxes.     
    2. lnd→atm:   if land grid resolution >> atmosphere resolution:  "mono"  
    3. lnd→atm:   if land grid resolution <= atmosphere resolution:   ESMF's bilin.  
    4. DESIRED:  a version of intbilin for FV source grids.   

...