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 43
    • Issues 43
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 13
    • Merge requests 13
  • 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
  • #88
Closed
Open
Issue created Oct 10, 2023 by aho@ahoMaintainer

Use case and example data

Hi @vagudets,

As I briefly commented yesterday, I think it'd be good to have some use cases and example data in this project. We have several example scripts and recipes now but from my experience as a user, it is not so straightforward to find all the pieces to run one case, and there is no description for the scripts yet.

We can create a few essential use cases that cover all the current usage, e.g., seasonal and decadal, multiple variables, using Autosubmit, etc. I think you know the most about how to create a minimal amount of use cases to cover all the functionality, e.g., if one case can include multiple variables and scorecards, we don't need two use cases. So if it's not a problem for you, you can create a list of examples and I can do the work (I may need some help for the part I'm not familiar with but we can tag people later.)

About example data, I'd say it is not so necessary but could be a good thing to have. In startR, we don't have saved data, and all the use cases use data from esarchive. The downside is that the data may disappear and the external people can't run the example without esarchive. IMO it would be good to have example data in SUNSET and we can use it to test modules and reduce the dependency on data archives.

It is not an urgent issue of course. Let me know what you think and we can discuss the details (like where to put the things and work distribution.)

Best,
An-Chi

Ps., CSTools example data can be used but not for all the cases, e.g., multi-variable, forecast data.

Assignee
Assign to
Time tracking