Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • C climix
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 51
    • Issues 51
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 5
    • Merge requests 5
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • climix
  • climix
  • Issues
  • #255

More user friendly application of choice of period (monthly, seasonal, annual, user specific...)

Right know the period on which the index is calculated is to be set in the yaml file

    period:
      allowed:
        annual:
        monthly:
        seasonal: 
      default: seasonal

and the default value is taken.

In case, like for klimatfabriken, one needs to calculate the index for multiple periods, it is very very error prone to have to change the default value in the yaml file, which lies somewhere long in the climix tree.

I think it is very necessary to add period to the parsed arguments from the command line, or find another solution.

Assignee
Assign to
Time tracking