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
  • Issues
  • #89
Closed
Open
Issue created Oct 16, 2023 by vagudets@vagudetsMaintainer

Allow Anomalies() to work when hcst and obs have different lat/lon dimensions

In the case that the anomalies must be computed before Downscaling or other operations that require hcst and obs to be in their original grids, CST_Anomaly() cannot be used. The problem is described in s2dv#108 (closed).

The proposed solution, at least for now, is to add the option to compute the anomalies with a simple mean in this particular case. If the user has requested cross-validation or other special methods, they will get a warning stating that these methods are not currently available for the case where hcst and obs have different grids.

The changes will be made in the branch dev-anomalies-downscaling.

FYI @aho @eduzenli @jramon

Assignee
Assign to
Time tracking