Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • startR startR
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 29
    • Issues 29
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 7
    • Merge requests 7
  • 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
  • Earth SciencesEarth Sciences
  • startRstartR
  • Issues
  • #133
Closed
Open
Issue created Feb 14, 2022 by aho@ahoMaintainer

CDO warning when CDORemapper is used

It is a long-term issue that when CDORemapper() is used, there are several warnings coming from CDO:

  • Progress: 0%Warning (find_time_vars): Time variable >time< not found! Warning (find_time_vars): Time variable >time< not found! Warning (find_time_vars): Time variable >time< not found! Warning (find_time_vars): Time variable >time< not found!

or

Warning (cdfScanVarAttr): NetCDF: Variable not found - lon_bnds

The results are correct so it is not a critical problem. According to this discussion https://code.mpimet.mpg.de/boards/1/topics/221, the warning might come from the lack of time variable. But our esarchive data always has time variable. It may be a problem in the temporal .nc file created by startR. This problem seems to happen when we changed to use CDO_1.9.8.

Edited Feb 15, 2022 by aho
Assignee
Assign to
Time tracking