orog_gsl

Structured YAML to run the component orog_gsl is validated by JSON Schema and requires the orog_gsl: block, described below. If orog_gsl is to be run via a batch system, the platform: block, described here, is also required.

Documentation for the UFS Utils orog_gsl program is here.

Here is a prototype UW YAML orog_gsl: block, explained in detail below:

orog_gsl:
  config:
    halo: 4
    input_grid_file: /path/to/C{{ orog_gsl.config.resolution }}_grid.tile{{ orog_gsl.config.tile }}.halo{{ orog_gsl.config.halo }}.nc
    resolution: 403
    tile: 7
    topo_data_2p5m: /path/to/geo_em.d01.lat-lon.2.5m.HGT_M.nc
    topo_data_30s: /path/to/HGT.Beljaars_filtered.lat-lon.30s_res.nc
  execution:
    batchargs:
      cores: 1
      walltime: "00:01:00"
    envcmds:
      - module use /path/to/modules
      - module load module_name
    executable: /path/to/orog_gsl
  rundir: /path/to/run/dir
platform:
  account: me
  scheduler: slurm

UW YAML for the orog_gsl: Block

config:

Configuration parameters for the orog_gsl component.

halo:

Halo number (-999 for no halo).

input_grid_file:

Path to the tiled input grid file.

resolution:

Input grid resolution index.

tile:

Tile number (1-6 for global, 7 for regional).

topo_data_2p5m:

Path to file containing global topographic data on 2.5-minute lat-lon grid.

topo_data_30s:

Path to file containing global topographic data on 30-second lat-lon grid.

execution:

See here for details.

rundir:

The path to the run directory.