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 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
  • Merge requests
  • !158

Set first forecast time as January for decadal models initialized in November

  • Review changes

  • Download
  • Patches
  • Plain diff
Merged vagudets requested to merge dev-Loading_decadal_start_in_January into master Aug 28, 2024
  • Overview 2
  • Commits 6
  • Pipelines 3
  • Changes 6

Some decadal models are initialized in November, meaning the first two forecast times correspond to November and December of the initialization year.

For the purposes of easilg building multimodel systems, these two first forecast times should be discarded, and "forecast time 1" should be considered as January.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: dev-Loading_decadal_start_in_January