Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • s2s-ai-challenge s2s-ai-challenge
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Aaron Spring
  • s2s-ai-challenges2s-ai-challenge
  • Issues
  • #22

Closed
Open
Created Jun 17, 2021 by Aaron Spring@aaron.spring🚼Owner

Definition of biweekly aggregates

How the biweekly aggregates for t2m and tp are calculated is not very well described and explained. You can see what I did in the renku dataset notebook. In this notebook I show how I get from climetlab data to the biweekly datasets used for scoring. However, I mixed up the lead_time definition for tp.

Working on the changes:

  • climetlab: https://github.com/ecmwf-lab/climetlab-s2s-ai-challenge/pull/24
  • website: https://github.com/s2s-ai-challenge/s2s-ai-challenge.github.io/pull/25
  • template: s2s-ai-challenge-template!14 (merged)
Edited Jun 18, 2021 by Aaron Spring
Assignee
Assign to
Time tracking

This GitLab is a part of renkulab.io