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
  • #68
Closed
Open
Issue created Feb 28, 2023 by vagudets@vagudetsMaintainer

Bug in recipe checker: System/Reference name check fails if an incorrect time horizon is provided

The recipe checker fails mid-check if a time horizon other than "Seasonal" or "Decadal" is provided, because it cannot find the corresponding archive.

ERROR [2023-02-28 11:57:58] The element 'Horizon' in the recipe must be one of the following: subseasonal, seasonal, decadal.
Error in recipe$Analysis$Datasets$System$name %in% names(archive$System) : 
  object 'archive' not found

Therefore, the check is not completed because the script fails before reaching the end.

Solution: Adding an extra condition to the name check.

Assignee
Assign to
Time tracking