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

Trend(): Bug in p-value when NAs exist

When the data for trend calculation is full of NA, .Trend() returns NAs for all the outputs (trend, conf.level, p.val, detrend.) p.val should only have dimension stats = 1, but now the function returns a vector of NA of length polydeg + 1. So, if the trend can be calculated (i.e., there is no time vector full of NAs), the returned p.val will have dimension stats = 1; but if there is any NA being returned, the dimension becomes stats = (ploydeg + 1) and the values are wrong (misplaced).

@nperez @vtorralba do you use Trend() to calculate p-value? This is a development for issue #1 (closed) opened by you and I'd like to know if you're impacted by this problem.

P.s., This bug is related to !27 (merged), which changed p.val <- NA to p.val <- rep(NA, polydeg + 1)

Best,
An-Chi

Assignee
Assign to
Time tracking