[R] why a moving average fun takes too long time!!

MacQueen, Don macqueen1 at llnl.gov
Wed Mar 20 20:06:46 CET 2013


This looks like a question for r-sig-geo.



-- 
Don MacQueen

Lawrence Livermore National Laboratory
7000 East Ave., L-627
Livermore, CA 94550
925-423-1062





On 3/20/13 8:02 AM, "Jonsson" <amen.alyaari at Bordeaux.inra.fr> wrote:

>I am calculating a moving average for 601 rasters (720, 1440)and it is
>taking
> a day to finish. I wonder if this is normal or something is wrong
>I am using Linux .
>
>code:
>
>        dir1 <- list.files("/home/spa4-358-4-365", "*.img", full.names =
>TRUE)
>        saf=stack(dir1)
>        meansmosas <-  overlay(saf,fun=function(x) movingFun(x,
>fun=mean,n=35, na.rm=TRUE))
>
>info:
>
>          saf
>           class       : RasterStack
>         dimensions  : 720, 1440, 1036800, 601  (nrow, ncol, ncell,
>nlayers)
>       resolution  : 0.25, 0.25  (x, y)
>       extent      : -180, 180, -90, 90  (xmin, xmax, ymin, ymax)
>         coord. ref. : +proj=longlat +datum=WGS84 +no_defs +ellps=WGS84
>+towgs84=0,0,0
>
>
>
>--
>View this message in context:
>http://r.789695.n4.nabble.com/why-a-moving-average-fun-takes-too-long-time
>-tp4661920.html
>Sent from the R help mailing list archive at Nabble.com.
>
>______________________________________________
>R-help at r-project.org mailing list
>https://stat.ethz.ch/mailman/listinfo/r-help
>PLEASE do read the posting guide
>http://www.R-project.org/posting-guide.html
>and provide commented, minimal, self-contained, reproducible code.



More information about the R-help mailing list