[R-sig-Geo] Fwd: Re: Problem creating raster brick (Lyndon Estes)

2011-11-21 Thread Swen Meyer
Dear Lydon, I also had some trouble with stacking Layers in the Raster package. Try to use a 32 bit version of R. Sounds weired but in my case the stacking with the Raster package was much faster using the Raster Package on a 32 bit - R Version. This is what Robert Hijmans once wrote me when I

Re: [R-sig-Geo] Fwd: Re: Problem creating raster brick (Lyndon Estes)

2011-11-21 Thread Lyndon Estes
Hi Swen, Thanks for the suggestion. That brings to mind an earlier problem I had with a different functions substituting values on large rasters, and I got around it by writing the following lines into the code: if(raster:::.toDisk() != TRUE) { setOptions(todisk = TRUE) cat("We don't

Re: [R-sig-Geo] Fwd: Re: Problem creating raster brick (Lyndon Estes)

2011-11-23 Thread Robert J. Hijmans
Lyndon, The reason might be that the large rasters trigger raster to processing by chunk (writing to disk) whereas the smaller file is considered small enough for processing in RAM. That may not be the case, and the OS may start swapping memory (using disk as RAM) which is slow. If this happens, yo

Re: [R-sig-Geo] Fwd: Re: Problem creating raster brick (Lyndon Estes)

2011-11-28 Thread Lyndon Estes
Hi Robert, Thanks for the response. I will continue to keep forcing a write to disk to prevent this from occurring. Based on this post, and another earlier in the year, I looked a bit more into other methods for calculating available RAM, at least for Linux and Mac systems. I understand from so