Il 19/10/2015 11:30, Markus Neteler ha scritto:
> The problem is to "guess" how much memory resources are available
> which change continuously (i.e. RAM is naturally static but its
> allocation not).
sure - perhaps taking the total memory as an upper bound could mitigate
at least the most
On Mon, Oct 19, 2015 at 9:01 AM, Paolo Cavallini wrote:
> Il 18/10/2015 11:48, Markus Neteler ha scritto:
>> On Fri, Oct 16, 2015 at 5:32 PM, Paolo Cavallini
>> wrote:
>>> Hi all.
>>> I cannot get r.contour working. It always takes a lot of CPU,
On Mon, Oct 19, 2015 at 11:35 AM, Paolo Cavallini wrote:
> Il 19/10/2015 11:30, Markus Neteler ha scritto:
>
>> The problem is to "guess" how much memory resources are available
>> which change continuously (i.e. RAM is naturally static but its
>> allocation not).
>
> sure
On Fri, Oct 16, 2015 at 5:32 PM, Paolo Cavallini wrote:
> Hi all.
> I cannot get r.contour working. It always takes a lot of CPU, then
> crashes. Anyone has more joy?
> grass 7.0.1-2 from Debian sid.
Please post your computational region settings (g.region -p).
Markus
Hi all.
I cannot get r.contour working. It always takes a lot of CPU, then
crashes. Anyone has more joy?
grass 7.0.1-2 from Debian sid.
Thanks.
--
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
___
>
> I cannot get r.contour working. It always takes a lot of CPU, then
>> crashes. Anyone has more joy?
>> grass 7.0.1-2 from Debian sid.
>>
>
>
> I just used this yesterday without issue, but with 7.1. Are the region
> settings correct and/or the increment between contours levels?
>
Mark