[GRASS-user] temporary maps/space during r.fill.dir execution

GRASS GRASS user
1

Hi grass users,

does anybody know how to avoid the temporary use of disk space during execution of r.fill.dir? For large input files it seems that large temporary files are written as well since I got messages like “no disk space left” (running in a minimized environment where not so much disk space is available).

Thanks a lot for any hints…

Regards,
Christian.

2

On Wed, Apr 14, 2010 at 11:01 AM, Christian Schwartze
<christian.schwartze@uni-jena.de> wrote:

Hi grass users,

does anybody know how to avoid the temporary use of disk space during
execution of r.fill.dir? For large input files it seems that large temporary
files are written as well since I got messages like "no disk space left"
(running in a minimized environment where not so much disk space is
available).

The command is actually memory demanding. What's the output of
g.region -p
? On how many cells do you work on?

Markus

3

g.region -p says:

    projection: 0 (x,y)
    zone: 0
    north: 6257261.73938969
    south: 6124108.23119424
    west: 650218.74629604
    east: 775529.77427479
    nsres: 84.32774427
    ewres: 69.6946763
    rows: 1579
    cols: 1798
    cells: 2839042

Hence, working on nearly 3 mill. cells...

Regards,
Christian.
--------------------------------------------------
From: "Markus Neteler" <neteler@osgeo.org>
Sent: Wednesday, April 14, 2010 10:07 PM
To: "Christian Schwartze" <christian.schwartze@uni-jena.de>
Cc: "GRASS user list" <grass-user@lists.osgeo.org>
Subject: Re: [GRASS-user] temporary maps/space during r.fill.dir execution

On Wed, Apr 14, 2010 at 11:01 AM, Christian Schwartze
<christian.schwartze@uni-jena.de> wrote:

Hi grass users,

does anybody know how to avoid the temporary use of disk space during
execution of r.fill.dir? For large input files it seems that large temporary
files are written as well since I got messages like "no disk space left"
(running in a minimized environment where not so much disk space is
available).

The command is actually memory demanding. What's the output of
g.region -p
? On how many cells do you work on?

Markus

4

Hi,

2010/4/14 Markus Neteler <neteler@osgeo.org>:

does anybody know how to avoid the temporary use of disk space during
execution of r.fill.dir? For large input files it seems that large temporary
files are written as well since I got messages like "no disk space left"
(running in a minimized environment where not so much disk space is
available).

The command is actually memory demanding. What's the output of

btw, is there any particular reason why data are kept in temp files
and then written to raster maps?

Martin

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa

5

On Wed, Apr 14, 2010 at 11:33 PM, Martin Landa <landa.martin@gmail.com> wrote:

Hi,

2010/4/14 Markus Neteler <neteler@osgeo.org>:

does anybody know how to avoid the temporary use of disk space during
execution of r.fill.dir? For large input files it seems that large temporary
files are written as well since I got messages like "no disk space left"
(running in a minimized environment where not so much disk space is
available).

The command is actually memory demanding. What's the output of

btw, is there any particular reason why data are kept in temp files
and then written to raster maps?

It gives the advantage to not destroy in --overwrite mode an existing
map when the new attempt fails or was interrupted by the user.

Markus