On 23/09/16 20:51, Rich Shepard wrote:
On Fri, 23 Sep 2016, Markus Metz wrote:
Apparently there are less than 52 MB of free memory left. The resulting
vector contours must be quite large. Try to export GRASS_VECTOR_LOWMEM=1
before running r.contour.
Maybe also use a larger step or less levels.
On Sat, 1 Oct 2016, Moritz Lennert wrote:
The mask limits the area in which data is read, so only the parts of the
dem inside the mask will be read, so contours will only be created for
that area. But if you want to make sure, create a very small mask area and
try ;-)
Moritz,
Thanks for con
Le 1 octobre 2016 14:42:49 GMT+02:00, Rich Shepard a
écrit :
>On Sat, 1 Oct 2016, Moritz Lennert wrote:
>
>> FYI: In grass7, r.mask has a 'vector' parameter which allows you
>create a
>> mask directly from a vector map.
>
>Moritz,
>
>I saw that and decided to try that today since I'm not having
On Sat, 1 Oct 2016, Glynn Clements wrote:
Is GRASS built for 32-bit (x86) or 64-bit (x86-64 aka amd64)? Running
"file" on e.g. r.contour will tell you.
Glynn,
No need to run file; this host is running a 32-bit CPU; the replacement
machine is 64-bit.
A 32-bit process can't use more than 4
On Sat, 1 Oct 2016, Moritz Lennert wrote:
FYI: In grass7, r.mask has a 'vector' parameter which allows you create a
mask directly from a vector map.
Moritz,
I saw that and decided to try that today since I'm not having the results
I want.
And AFAIK, no need to g.copy. Just run your analys
On 23/09/16 20:51, Rich Shepard wrote:
On Fri, 23 Sep 2016, Markus Metz wrote:
Apparently there are less than 52 MB of free memory left. The resulting
vector contours must be quite large. Try to export GRASS_VECTOR_LOWMEM=1
before running r.contour.
Maybe also use a larger step or less levels.
Rich Shepard wrote:
>I assumed that grass did not see the available memory, but did not realize
> it would not use the available swap memory.
Is GRASS built for 32-bit (x86) or 64-bit (x86-64 aka amd64)? Running
"file" on e.g. r.contour will tell you.
A 32-bit process can't use more than 4
On Fri, 23 Sep 2016, Markus Metz wrote:
Apparently there are less than 52 MB of free memory left. The resulting
vector contours must be quite large. Try to export GRASS_VECTOR_LOWMEM=1
before running r.contour.
Maybe also use a larger step or less levels.
Took a different approach by reduci
On Fri, 23 Sep 2016, Markus Metz wrote:
Apparently there are less than 52 MB of free memory left. The resulting
vector contours must be quite large. Try to export GRASS_VECTOR_LOWMEM=1
before running r.contour.
Maybe also use a larger step or less levels.
Markus,
Tried both. Still cannot co
On Fri, 23 Sep 2016, Markus Metz wrote:
Apparently there are less than 52 MB of free memory left. The resulting
vector contours must be quite large. Try to export GRASS_VECTOR_LOWMEM=1
before running r.contour.
Markus,
I assumed that grass did not see the available memory, but did not reali
On Thu, Sep 22, 2016 at 5:45 PM, Rich Shepard wrote:
> A possible bug in ../diglib/cindex.c.
>
> This host has 4G RAM and 16G swap memory. With X running top shows 740M
> RAM and 15.3G swap free. I'm trying to run a spatial analysis program which
> fails after 2.5-4.7 hours (depending on the c
A possible bug in ../diglib/cindex.c.
This host has 4G RAM and 16G swap memory. With X running top shows 740M
RAM and 15.3G swap free. I'm trying to run a spatial analysis program which
fails after 2.5-4.7 hours (depending on the contour resolutions). This
morning after 2.5 hours it failed wi
12 matches
Mail list logo
