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
  • #57
Closed
Open
Issue created Jan 19, 2023 by vagudets@vagudetsMaintainer

Allow user to specify variable units

@nperez proposed this as a feature. Opening this issue for any discussion related to this development.

Users would specify the desired units in the recipe, for example:

  Variables:
    name: tas
    units: K
    freq: monthly_mean 

Then the unit conversion, if needed, would be done at the beginning of the workflow after loading the data.

Currently unit conversion is always done for the case of precipitation (see #38 (closed) and #56 (closed)), accompanied by an INFO message. Some special considerations might be necessary for this particular case.

Assignee
Assign to
Time tracking