chgres_cube

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

• This driver receives a cycle argument, which it makes available as a Python datetime object to Jinja2 when realizing its input config. This supports specification of cycle-specific values. For example, the key-value pair

  gfs.t{{ cycle.strftime('%H') }}z.atmanl.nc: /some/path/{{ cycle.strftime('%Y%m%d%H') }}/gfs.t{{ cycle.strftime('%H') }}z.atmanl.nc
  

  would be rendered as

  gfs.t18z.atmanl.nc: /some/path/2024021218/gfs.t18z.atmanl.nc
  

  for cycle 2024-02-12T18.

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

chgres_cube:
  execution:
    executable: chgres_cube
    mpiargs:
      - "--export=NONE"
    mpicmd: srun
    threads: 1
  namelist:
    update_values:
      config:
        atm_files_input_grid: atm.t{{cycle.strftime('%H') }}z.nc
        convert_atm: true
        convert_nst: true
        convert_sfc: true
        cycle_day: !int "{{ cycle.strftime('%d') }}"
        cycle_hour: !int "{{ cycle.strftime('%H') }}"
        cycle_mon: !int "{{ cycle.strftime('%m') }}"
        data_dir_input_grid: /path/to/data/{{ cycle.strftime('%Y%M%d%H') }}
        fix_dir_target_grid: /path/to/fixdir
        grib2_file_input_grid: a.file.gb2
        mosaic_file_target_grid: /path/to/mosaic/C432.mosaic.halo4.nc
        orog_files_target_grid: /path/to/orog/C432.oro_data.tile7.halo4.nc
        sfc_files_input_grid: sfc.t{{cycle.strftime('%H') }}z.nc
        varmap_file: /path/to/varmap_table
        vcoord_file_target_grid: /path/to/global_hyblev.l65.txt
    validate: true
  rundir: /path/to/dir
platform:
  account: me
  scheduler: slurm

UW YAML for the chgres_cube: Block

execution

See this page for details.

namelist

Supports base_file: and update_values: blocks (see Updating Values for details). Namelist options are described here.

Before the namelist file is written, its proposed content will be validated against the appropriate schema. This can be suppressed by setting validate: false in the UW YAML configuration block for the namelist.

rundir

The path to the run directory.