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
Doing a logical operation with a DCELL raster within an if(x,a) statement
produces an error: "Incorrect argument types to function bitand()".
This doesn't seem to be described inside the docs, is it?
When the if() function is described it only states its behaviour in case of
NULL, 0 or
On Mon, Oct 19, 2015 at 5:18 PM, G. Allegri wrote:
> Doing a logical operation with a DCELL raster within an if(x,a) statement
> produces an error: "Incorrect argument types to function bitand()".
> This doesn't seem to be described inside the docs, is it?
>
That sounds like
Hi,
I had the same problem some time ago, and just kept the "^" in
µg/m^3 because i didn't find superscript format nor in d.text (or the gui
to add text) neither in ps.map...
But maybe in your case you can use mg/ha to avoid the ^?
Cheers,
Vero
2015-10-18 21:41 GMT-03:00 Davies, Kalu
GRASS 6.4.4 on Windows.
giovanni
Il 19/ott/2015 17:52, "Paulo van Breugel" ha
scritto:
>
>
> On Mon, Oct 19, 2015 at 5:18 PM, G. Allegri wrote:
>
>> Doing a logical operation with a DCELL raster within an if(x,a) statement
>> produces an error:
On Mon, Oct 19, 2015 at 12:05 PM, Glynn Clements
wrote:
>
> Dylan Beaudette wrote:
>
>> Are there any reasons to prefer sequential operations (that do not
>> alter the region) vs. parallel operations?
>
> Running additional jobs in parallel is only worthwhile if the
>
Dylan Beaudette wrote:
> Are there any reasons to prefer sequential operations (that do not
> alter the region) vs. parallel operations?
Running additional jobs in parallel is only worthwhile if the
resources which they would use (CPU, memory, I/O bandwidth) would
otherwise be idle.
Once you
That's what disappointed my client (and me) Glynn: why integer yes and not
floats? Is it a technical limitation or there's a ratio behind it?
Anyway did I miss something from the docs? I couldn't find it.
Why do you that I'm confusing the operators? I've always talked about
logical operators...
G. Allegri wrote:
> Doing a logical operation with a DCELL raster within an if(x,a) statement
> produces an error: "Incorrect argument types to function bitand()".
First, you're confusing bitwise operators and logical operators. & and
| are bitwise operators, while && and || (and &&& and |||)
11 matches
Mail list logo