Skip to content

User story: model run descriptions #311

@alistairsellar

Description

@alistairsellar

This user story summarises the requirement for how CMEW should handle descriptions of each model run. This is two stories in a single issue. They are closely related, or at least I had previously conflated them.

Plot labelling

  • As someone viewing CMEW outputs,
  • I need each run to be consistently labelled in all plots, with a string provided by the CMEW user,
  • So that I can rapidly understand what each run represents in the CMEW outputs.

Implementation notes:

  • This means that the CMEW user should be required to provide a mandatory variable LABEL_FOR_PLOTS for each run.
  • It also means that all CMEW recipes should make use of that label in plots, via the alias facet in dataset specifications in the recipe.
  • Implement consistent plot labelling in CMEW #260 is the main issue associated with the first requirement, and has sub-issues for investigations and implementation.

File naming

  • As a CMEW user,
  • I want CMEW files associated with my run (standardised data, ESMValTool outputs such as plots) to be named in a meaningful way,
  • So that I can more easily debug or find individual files.

Implementation ideas:

Sub-issues

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions