Skip to content

setup_xml error #2955

Closed Answered by aerorahul
benjamin-cash asked this question in Q&A
Sep 24, 2024 · 2 comments · 4 replies
Discussion options

You must be logged in to vote

@benjamin-cash
There are unresolved templates in the yaml you had provided.
The best way to provide a yaml, is to include the defaults and then over-ride with user specific options.

Here is an edit of your yaml that works:

defaults:
  !INC {{ HOMEgfs }}/parm/config/gefs/yaml/defaults.yaml
base:
  DO_JEDIATMVAR: "NO"
  DO_JEDIATMENS: "NO"
  DO_JEDIOCNVAR: "NO"
  DO_JEDISNOWDA: "NO"
  DO_MERGENSST: "NO"
  FHMAX_GFS: 2976
  FHMAX_HF_GFS: 0
  KEEPDATA: "NO"
  REPLAY_ICS: "YES"
  DO_EXTRACTVARS: "NO"
  FLTFILEGFS: "postxconfig-NT-SFS.txt"
  FLTFILEGFSF00: "postxconfig-NT-SFS.txt"
  ACCOUNT: {{ 'HPC_ACCOUNT' | getenv }}
  HPSS_PROJECT: "emc-marine"
  BASE_CPLIC: {{ 'TOPICDIR' | getenv }}/REPLAY…

Replies: 2 comments 4 replies

Comment options

You must be logged in to vote
1 reply
@aerorahul
Comment options

Comment options

You must be logged in to vote
3 replies
@aerorahul
Comment options

@aerorahul
Comment options

Answer selected by benjamin-cash
@benjamin-cash
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants