...
- 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)
- The transpose of the SE→FV mono map:
- ./GenerateTransposeMap --in map_atm2ocn_mono.nc --out map_ocn2atm_monotr.nc
- 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)
- The transpose of the SE→FV intbilin map. No negative weights, but weights can be larger than 1.
- ./GenerateTransposeMap --in map_atm2ocn_intbilin.nc --out map_ocn2atm_intbilintr.nc
- FV→FV mono (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). Paul Ullrich please confirm!
UPDATE 2020/2/21: Removing highorder maps which can have negative weights. It's probably a bad idea to use negative weights in a coupled simulation, and we shouldn't recommend this without detailed evaluation.
...