Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • C climix
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 53
    • Issues 53
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • Deployments
    • Deployments
    • Releases
  • 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
  • #158

Closed
Open
Created Feb 06, 2020 by Lars Bärring@a001257Developer

Question: parameter long name

@a002160 I saw that there is a reasonable long name for the threshold parameter of nzero. Currently this have to be added manually in the yaml file. Could we devise a ways to have it already in the master table? This issue resurfaced now when I am working on the running_statistics [and thresholded_running_statistics] index function. Here we have a parameter window_size of kind: quantity and units: days. And I cannot find a relevant standard name (other than time) that has the right canonical units. So, either we ...

  • ... are stuck with adding this manually to the yaml file
  • ... accept that the auxiliary coordinate will have neither standard_name nor long_name, only var_name "window_size"
  • ... find a way to write this into in the master table

Any thoughts? For now, I would be reluctant to open a CF ticket to add a standard name involving anything resembling time/duration or similar...

Assignee
Assign to
Time tracking