[GRASS-dev] Re: [GRASS GIS] #520: r.terraflow/iostream does not
respect STREAM_DIR option
GRASS GIS
trac at osgeo.org
Sun Jul 19 15:53:58 EDT 2009
#520: r.terraflow/iostream does not respect STREAM_DIR option
---------------------+------------------------------------------------------
Reporter: mmetz | Owner: grass-dev at lists.osgeo.org
Type: defect | Status: new
Priority: major | Milestone: 6.4.0
Component: Raster | Version: svn-develbranch6
Resolution: | Keywords: r.terraflow, tmp
Platform: All | Cpu: All
---------------------+------------------------------------------------------
Comment (by neteler):
Replying to [comment:20 mmetz]:
> Replying to [comment:19 hamish]:
> > Replying to [comment:18 mmetz]:
> > ISTR that the Terraflow team (Andrew? Laura?) explained why they used
that a long time ago (I now forget exact reason),
Most likely because r.terraflow wasn't originally written for GRASS/was
written also as stand-alone version.
> Picking a directory whose contents are deleted automatically if I
remember right, which would be the case for $MAPSET/.tmp/$MACHINE.
Perfect. I assume that 99% of the users will never inspect any tmp file of
r.terraflow. So that is a perfect default. If a specialist wants to
inspect, then define a different directory +in that case*.
> > Note that these temp files may be >2gig
>
> I get regularly >20GB, having to work on somewhat larger datasets.
Thinking about Doug's datasets, it would go way above 100GB.
Yes, and I always forget to look in /var/tmp/ for undeleted rubbish (but
check instead my HOME for delete candidates). Having auto-deletion of tmp
stuff left by interrupted/crashed r.terraflow runs when leaving GRASS
would be a major advantage for most users.
> > (use the memory= option to lower those needs), and they may be
potentially useful(?) for inspection/archive/debugging/reuse later, so
keeping them completely hidden may not be desired.
As said, who wants to analyse these files is also able to change a default
setting.
> These files are deleted upon successful completion of the module using
the iostream lib, nothing left to inspect. They are probably only useful
for the iostream lib developers for debugging. Same for the segment lib,
intermediate files are probably only useful for developers working on the
segment lib. I don't see a reason why files created by the iostream
library should be treated differently to files created by the segment
library, or vice versa, when it comes to their storage location.
+1
> This discussion is now moving away from r.terraflow towards where to
store large temporary files, maybe this ticket can be closed and the
discussion be continued somewhere else if needed?
No, still /var/tmp/ is the default also in GRASS 7. This should be
changed.
MarkusN
> Markus M
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/520#comment:21>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list