orog

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

Documentation for the UFS Utils orog program is here.

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

orog:
  execution:
    batchargs:
      cores: 1
      walltime: 00:05:00
    executable: /path/to/orog
  files_to_link:
    fort.15: /path/to/fix/thirty.second.antarctic.new.bin
    landcover30.fixed: /path/to/fix/landcover30.fixed
    fort.235: /path/to/fix/gmted2010.30sec.int
  grid_file: /path/to/netcdf/grid/file
  rundir: /path/to/run/dir
platform:
  account: me
  scheduler: slurm

UW YAML for the orog: Block

old_line1_items

Configuration parameters for the orog component corresponding to the first line entries prior to hash 57bd832 from (July 9, 2024). If using this section, a value for orog_file should also be provided.

execution:

See here for details.

files_to_copy:

See this page for details.

files_to_hardlink:

Identical to files_to_copy: except that hard links will be created in the run directory instead of copies, when possible. Otherwise a copy will be created.

files_to_link:

Identical to files_to_copy: except that symbolic links will be created in the run directory instead of copies.

mask:

Boolean indicating whether only the land mask will be generated. Defaults to false.

merge:

Path to an ocean merge file.

orog_file:

Path to an output orography file if using a version of UFS_UTILS prior to hash 57bd832 from (July 9, 2024). If using this section, values for old_line1_items should also be provided.

rundir:

The path to the run directory.