Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • SUNSET SUNSET
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 42
    • Issues 42
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Earth SciencesEarth Sciences
  • SUNSETSUNSET
  • Issues
  • #52
Closed
Open
Issue created Jan 04, 2023 by vagudets@vagudetsMaintainer

Include parameters in recipe to let users choose which data to save/plot

This was requested in #27 (closed)

Opening this issue to keep track of the potentials ways we can handle this.

TODOs (Saving):

  • Anomalies
  • Calibration
  • Skill
  • Probabilities
  • Downscaling
  • Visualization
  • Change unit tests
  • Update recipes

TODOs (Visualization):

  • Update recipes

Other tasks:

  • Update recipe checker

Saving Option 1: Including parameters inside the configuration of every module

  Workflow:
    Anomalies:
      compute: yes
      cross_validation: yes 
    Calibration:
      method: raw
      save_experiment: yes/no # saves hcst/fcst
      save_observations: yes/no # saves the corresponding observations
    Skill:
      metric: RPSS CRPSS EnsCorr
      save_metrics: yes/no # save the skill metrics
    Probabilities:
      percentiles: [[1/3, 2/3], [1/10, 9/10]]
      save_probabilities: yes/no
      save_percentiles: yes/no 
# ... etc

Potential issues: ensuring flexibility and consistency if Anomalies are computed, given that the user has the option to compute them before or after the Calibration step.

Saving Option 2: Adding a Saving section inside 'Workflow':

  Workflow:
    # (...)
    Saving:
      outputs: skill # possibilities: skill, experiment, observations, probabilities, percentiles
      ## Add possible options for significance?
# ... etc

Potential issues: Not as user-friendly and clear as Option 1

Visualization Option 1: Adding a Visualization section inside 'Workflow':

  Workflow:
    # (...)
    Visualization:
      plots: most_likely_terciles, skill # possibilities: skill, forecast_ensemble_mean, most_likely_terciles
      ## Add possible options for significance?
# ... etc
Edited Oct 05, 2023 by vagudets
Assignee
Assign to
Time tracking