#23 Start to add schema for static sources in pp yamls

[singhd789]

No description provided.

[ceblanton]

Pretty good! I think we would like variables to be within the history file or offline history file, if possible, and I wasn't sure if history_file was offline or from the model output.

[singhd789]

Thanks @J-Lentz for the catches!

[ceblanton]

Looking good! I still think the variables has to be a element (?? not sure the yaml hame) within sources or offline_sources instead of a peer of sources and offline_sources. Let's discuss...

[ceblanton]

A tiny nit.. "history file" implies model output. Not sure what to call it though!

[singhd789]

offline diagnostic?

[ceblanton]

Yep, that works!

[singhd789]

Looking good! I still think the variables has to be a element (?? not sure the yaml hame) within sources or offline_sources instead of a peer of sources and offline_sources. Let's discuss...

I agree with this schema of

  components:
    - type: 'ocean'
      sources: ["ocean_month", "ocean_daily"]
      static:
        - sources: ["ocean_static"]
          variables: ["hgfeou"]
        - sources: ["ocean_bgc_static"]
        - offline_sources: ["/home/c2b/cmip6/offline/ocean_grids.nc"]
          variables: ["deptho", "sftof"]
        - offline_sources: ["/home/c2b/cmip6/offline/basins.nc"]

I believe the schema reflects that now as well (at least it appeared valid in my slight tests). @J-Lentz - do you know if the schema currently reflects this kind of yaml format?