Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • kadlu kadlu
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 17
    • Issues 17
    • 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
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • public_projects
  • kadlukadlu
  • Issues
  • #57

Closed
Open
Created Apr 07, 2020 by Oliver Kirsebom@kirsebomOwner

interpolation of 2D variables

My understanding is that currently all 2D variables are being passed to the interpolator as if they were on a irregular grid. (i.e. lat, lon, values are all 1d arrays.) This is necessary for CHS bathymetry data, but not really for wind speeds and wave heights, which come on a regular grid when downloaded from WWIII or ERA5. While the interpolator can handle irregular grids, the implementation is slow and memory heavy. Therefore, when possible we should keep data on regular grids. @matt_s , how difficult would it be to change this behaviour?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking