[R-sig-Geo] Raster memory problem

Marie Auger-Methe marie.augermethe at gmail.com
Wed Dec 12 22:14:33 CET 2012


Thanks for the replies.

changing the raster options as suggested by Jacob fixed the problem. I 
lowered the maxmemory:
rasterOptions(maxmemory=90000000)
rather than changing the todisk option. It worked like a charm.

Thanks!

Marie



On 12/12/2012 8:24 PM, Jacob van Etten wrote:
> Take a look at setOptions to force disk to disk.
>
> raster will guess if it can do the operation in memory but occasionally underestimates the memory available or required.
>
> Sent from my iPhone
>
> On 12/12/2012, at 15:20, Raffaele Morelli <raffaele.morelli at gmail.com> wrote:
>
>> 2012/12/12 Marie Auger-Methe <marie.augermethe at gmail.com>
>>
>>> Dear list,
>>>
>>> I am using large raster bricks for my analyses and I am running out of
>>> memory. I get the following message:
>>>
>>> Error: cannot allocate vector of size 231.0 Mb
>>>
>>> and this whether I do all my brick manipulations by loading the brick in
>>> R's memory or not (i.e., whether I use the option filename="name of my
>>> file").
>>> The strangest characteristic of the problem I have is that I get an
>>> error message when I handle smaller brick and not when handle larger brick.
>>>
>>> I have clean up my computer, defragmented it, increase my virtual
>>> memory, etc, and I still get an error.
>>>
>>> Any help will be greatly appreciated,
>>>
>>> Marie
>>
>> Welcome to the band called "Three of us (can't handle such big rasters)"
>> ;-)
>>
>> -raffaele
>>
>>    [[alternative HTML version deleted]]
>>
>> _______________________________________________
>> R-sig-Geo mailing list
>> R-sig-Geo at r-project.org
>> https://stat.ethz.ch/mailman/listinfo/r-sig-geo
> _______________________________________________
> R-sig-Geo mailing list
> R-sig-Geo at r-project.org
> https://stat.ethz.ch/mailman/listinfo/r-sig-geo



More information about the R-sig-Geo mailing list