Skip to content

Refinediag and preanalysis yaml specification #701

@ceblanton

Description

@ceblanton

Is your feature request related to a problem? Please describe.
Refinediag functionality (as defined in Bronx) was developed in Canopy's flow.cylc as a Jinja2/rose-suite setting. We hadn't yet expressed the refinediag (and its cousin that does not generate output, preanalysis) in the yaml configuration.

It's now time to do this, plus require the user scripts to specify their inputs and outputs explicitly. This has long been desired to make refineDiag script requirements known to the workflow.

Describe the solution you'd like
Each refinediag script must specify its inputs and outputs, and each preanalysis script must specify its inputs. The "label" or name of the script is arbitrary and only used for task name organization.

postprocess:
  preanalysis:
    vitals:
      script: "/path/to/vitals-script"
      input: ['atmos_month', 'aerosol_month']
  refinediag:
    ocean:
      script: "/path/to/ocean-script"
      input: ['ocean_monthly', 'ocean_bgc']
      output: ['ocean_refined']
    aerosol:
      script: "/path/to/aerosol-script"
      input: ['aerosol_month']
      output: ['aerosol_refined']

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions