[GRASS-dev] r.viewshed -memory problem

GRASS GIS GRASS GIS developer
1

Hi Folks,
I am try to use GRASS7 SVN on win 7. I tested new modul r.viewshed on
large dataset. But some problem with memory.
not shure if it is my mistake or bug.
Jan Trochta

r.viewshed -e --overwrite --verbose input=STRomy@boubin output=pk
coordinate=-803821.575747913,-1158866.72289775 max_dist=1500
Memory manager registering memory in MM_WARN_ON_MEMORY_EXCEEDED mode.
Nodata value set to -1.#QNAN0
rows=14293, cols=12816, total = 183179088
In-memory memory usage is 18318011328 B (17469 MB), max mem
allowed=524288000 B(500MB)
***** EXTERNAL_MEMORY MODE *****
Intermediate files will not be deleted in case of
abnormal termination.
To save space delete these files manually!
Estimated size active structure:
(key=64, ptr=4, total node=80 B)
Total= 1143440 B
Start sweeping.
Computing events ...
Sorting events...
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 2520B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 2598B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 2676B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 2754B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 2832B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 2910B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 2988B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3066B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3144B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3222B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3300B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3378B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3456B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3534B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3612B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3690B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3768B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3846B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3924B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 4002B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 4080B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 4158B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 4236B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 4314B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 4392B.
ami_single_temp_name: mktemp failed: : File exists
Assertion failed: 0, file ami_stream.cpp, line 97
This application has requested the Runtime to terminate it
in an unusual way.
Please contact the application's support team for more
information.
(Tue Jan 10 12:57:51 2012) Command finished (17 min 22 sec)

2

On Tue, Jan 10, 2012 at 1:03 PM, Jan Trochta <j.trochta@gmail.com> wrote:

Hi Folks,
I am try to use GRASS7 SVN on win 7. I tested new modul r.viewshed on
large dataset. But some problem with memory.
not shure if it is my mistake or bug.
Jan Trochta

r.viewshed -e --overwrite --verbose input=STRomy@boubin output=pk
coordinate=-803821.575747913,-1158866.72289775 max_dist=1500
Memory manager registering memory in MM_WARN_ON_MEMORY_EXCEEDED mode.
Nodata value set to -1.#QNAN0
rows=14293, cols=12816, total = 183179088
In-memory memory usage is 18318011328 B (17469 MB), max mem
allowed=524288000 B(500MB)
***** EXTERNAL_MEMORY MODE ****

...

please also post the output of
g.region -p

Markus

3

On Tue, Jan 10, 2012 at 1:03 PM, Jan Trochta <j.trochta@gmail.com> wrote:

Hi Folks,
I am try to use GRASS7 SVN on win 7. I tested new modul r.viewshed on
large dataset. But some problem with memory.
not shure if it is my mistake or bug.
Jan Trochta

The memory-related warnings can be ignored. The limit of 500MB is
exceeded by 4MB or 0.8%, nothing tragic. The error
ami_single_temp_name: mktemp failed: : File exists
is tragic, however.

The problem could be related to wrong directory separators used by
ami_single_temp_name (/ instead of \), needs testing. But it's
definitively not your mistake.

Markus M

r.viewshed -e --overwrite --verbose input=STRomy@boubin output=pk
coordinate=-803821.575747913,-1158866.72289775 max_dist=1500
Memory manager registering memory in MM_WARN_ON_MEMORY_EXCEEDED mode.
Nodata value set to -1.#QNAN0
rows=14293, cols=12816, total = 183179088
In-memory memory usage is 18318011328 B (17469 MB), max mem
allowed=524288000 B(500MB)
***** EXTERNAL_MEMORY MODE *****
Intermediate files will not be deleted in case of
abnormal termination.
To save space delete these files manually!
Estimated size active structure:
(key=64, ptr=4, total node=80 B)
Total= 1143440 B
Start sweeping.
Computing events ...
Sorting events...
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 2520B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 2598B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 2676B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 2754B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 2832B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 2910B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 2988B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3066B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3144B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3222B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3300B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3378B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3456B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3534B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3612B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3690B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3768B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3846B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3924B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 4002B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 4080B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 4158B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 4236B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 4314B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 4392B.
ami_single_temp_name: mktemp failed: : File exists
Assertion failed: 0, file ami_stream.cpp, line 97
This application has requested the Runtime to terminate it
in an unusual way.
Please contact the application's support team for more
information.
(Tue Jan 10 12:57:51 2012) Command finished (17 min 22 sec)
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

4

I tried decrease resolution to 0.2 and its work.

g.region -p:

projection: 99 (Krovak)
zone: 0
datum: towgs84=570.8,85.7,462.8,4.998,1.587,5.261,3.56
ellipsoid: bessel
north: -1158293.493
south: -1159681.061
west: -804210.292
east: -803341.459
nsres: 0.09999769
ewres: 0.1000038
rows: 13876
cols: 8688
cells: 120554688

Jan

Dne 10. ledna 2012 14:09 Markus Metz
<markus.metz.giswork@googlemail.com> napsal(a):

On Tue, Jan 10, 2012 at 1:03 PM, Jan Trochta <j.trochta@gmail.com> wrote:

Hi Folks,
I am try to use GRASS7 SVN on win 7. I tested new modul r.viewshed on
large dataset. But some problem with memory.
not shure if it is my mistake or bug.
Jan Trochta

The memory-related warnings can be ignored. The limit of 500MB is
exceeded by 4MB or 0.8%, nothing tragic. The error
ami_single_temp_name: mktemp failed: : File exists
is tragic, however.

The problem could be related to wrong directory separators used by
ami_single_temp_name (/ instead of \), needs testing. But it's
definitively not your mistake.

Markus M

r.viewshed -e --overwrite --verbose input=STRomy@boubin output=pk
coordinate=-803821.575747913,-1158866.72289775 max_dist=1500
Memory manager registering memory in MM_WARN_ON_MEMORY_EXCEEDED mode.
Nodata value set to -1.#QNAN0
rows=14293, cols=12816, total = 183179088
In-memory memory usage is 18318011328 B (17469 MB), max mem
allowed=524288000 B(500MB)
***** EXTERNAL_MEMORY MODE *****
Intermediate files will not be deleted in case of
abnormal termination.
To save space delete these files manually!
Estimated size active structure:
(key=64, ptr=4, total node=80 B)
Total= 1143440 B
Start sweeping.
Computing events ...
Sorting events...
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 2520B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 2598B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 2676B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 2754B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 2832B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 2910B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 2988B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3066B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3144B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3222B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3300B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3378B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3456B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3534B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3612B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3690B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3768B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3846B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 3924B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 4002B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 4080B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 4158B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 4236B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 4314B.
MM warning: limit=524288000B. allocating 261881248B. limit
exceeded by 4392B.
ami_single_temp_name: mktemp failed: : File exists
Assertion failed: 0, file ami_stream.cpp, line 97
This application has requested the Runtime to terminate it
in an unusual way.
Please contact the application's support team for more
information.
(Tue Jan 10 12:57:51 2012) Command finished (17 min 22 sec)
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

5

On Tue, Jan 10, 2012 at 2:15 PM, Jan Trochta <j.trochta@gmail.com> wrote:

I tried decrease resolution to 0.2 and its work.

g.region -p:

projection: 99 (Krovak)
zone: 0
datum: towgs84=570.8,85.7,462.8,4.998,1.587,5.261,3.56
ellipsoid: bessel
north: -1158293.493
south: -1159681.061
west: -804210.292
east: -803341.459
nsres: 0.09999769
ewres: 0.1000038
rows: 13876
cols: 8688
cells: 120554688

Ja,

do you really have a 10cm (!) resolution DEM there?
Perhaps you want to adjust the resolution to that of the DEM.

Best
Markus

6

Yes, Its 10 cm, but it is not DEM.I wish to simulate lidar scanning in
forest. I would like to know how far can terrestrial lidar find trees.
Thats why I have so detailed resolution.
Jan

Dne 10. ledna 2012 22:06 Markus Neteler <neteler@osgeo.org> napsal(a):

On Tue, Jan 10, 2012 at 2:15 PM, Jan Trochta <j.trochta@gmail.com> wrote:

I tried decrease resolution to 0.2 and its work.

g.region -p:

projection: 99 (Krovak)
zone: 0
datum: towgs84=570.8,85.7,462.8,4.998,1.587,5.261,3.56
ellipsoid: bessel
north: -1158293.493
south: -1159681.061
west: -804210.292
east: -803341.459
nsres: 0.09999769
ewres: 0.1000038
rows: 13876
cols: 8688
cells: 120554688

Ja,

do you really have a 10cm (!) resolution DEM there?
Perhaps you want to adjust the resolution to that of the DEM.

Best
Markus