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

Bugfix for global longitude + cross meridian case.

  • Review changes

  • Download
  • Patches
  • Plain diff
Merged aho requested to merge develop-lon-global-across_meridian into master Apr 01, 2020
  • Overview 1
  • Commits 5
  • Pipelines 0
  • Changes 2

The problem happened when longitude was requested globally but also across the circular border. For example,

  repos <- "/esarchive/exp/ecmwf/system5_m1/monthly_mean/tas_f6h/$var$_$sdate$.nc"
  var <- 'tas'
  lon.min <- 0
  lon.max <- 359.723  # bigger than the real maximum longitude in netCDF file but smaller than 360
  lat.min <- -90
  lat.max <- 90
  data <- Start(dat = repos,
                var = var,
                sdate = c('20170101', '20170401'),
                ensemble = indices(1),
                time = indices(1),
                latitude = values(list(lat.min, lat.max)),
                latitude_reorder = Sort(decreasing = T),
                longitude = values(list(lon.min, lon.max)),
                longitude_reorder = CircularSort(-180, 180),
                return_vars = list(time = 'sdate',
                                   longitude = NULL,
                                   latitude = NULL),
                retrieve = FALSE
               )

The output longitude dimension length should be 1296, while it was 1297. The repetitive value happened in lon = 0. This development fixes this mistake.

Edited Apr 02, 2020 by aho
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: develop-lon-global-across_meridian