Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
I ICOADS R HOSTACE
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 7
    • Issues 7
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • brivas
  • ICOADS R HOSTACE
  • Issues
  • #7

Closed
Open
Created May 29, 2020 by brivas@brecinosrivasMaintainer

get_gap_pos(interval, for.gaps) in find_gap

Additionally the sample from the profiler marks additional resources spend in:

-Line #36 in find_gap_func.R

Which is a call of the get_gap_pos() func

(this still needs to be double checked with the Rprof output from JASMIN)

This is the second output of profiler that points to this line. My command-line-run of Rprof() for one month only also points to line #36

It appears the code spend quite some time in get_gap_pos() func line #64

xx.int<-data.frame(date=miss,lon=lon.miss,lat=lat.miss)

might be the creation of a dataframe here. So is not as severe as the subset()

Again I will add output from the Rprof Jasmin run in comments below if this line keeps popping up in a different sample of Months/data

Edited May 29, 2020 by brivas
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking