Details Ticket 4269


Comment | Reply | Take | Resolve


Serial Number 4269
Subject problems with r.contour
Area grass6
Queue grass
Requestors giorgio.agugiaro@unipd.it
Owner none
Status open
Last User Contact Mon Apr 10 10:47:55 2006 (2 yr ago)
Current Priority 30
Final Priority 70
Due No date assigned
Last Action Mon Apr 10 11:11:45 2006 (2 yr ago)
Created Sat Apr 8 18:29:45 2006 (2 yr ago)

Transaction History Ticket 4269


Sat, Apr 8 2006 18:29:45    Request created by guest  
Subject: problems with r.contour

Platform: GNU/Linux/x86
grass obtained from: Trento Italy site
grass binary for platform: Compiled from Sources
GRASS Version: 6.1.cvs-2006.04.08

hello!

working with r.contour I experienced following things:

Location: Spearfish
Mapset: grass_new (yes, I am trying out the new grass 6.1.cvs against the "old"
2006.02.25 ;-)

from shell:

g.region rast=elevation.dem@PERMANENT
g.region -p
r.contour input=elevation.dem@PERMANENT output=dem_isoipse_050 step=50 cut=0
I get the usual list of errors and then the vecotr map is created.
then

g.remove vect=dem_isoipse_050
g.region res=1
r.contour input=elevation.dem@PERMANENT output=dem_isoipse_050 step=50 cut=0
I get a program abnormal end (killed) at:

Reading data.
Percent complete: Killed

what happened? could it be possible to have some more explanatory output?

on the other hand using the r.contour GUI, I noticed that selecting the "suppress
single crossing error messages" (this and only this) kills both the gui and the
d.m (as well as gis.m).

ciao!

giorgio
Mon, Apr 10 2006 10:47:55    Mail sent by msieczka  
Giorgio wrote:

> r.contour input=elevation.dem@PERMANENT output=dem_isoipse_050 step=50 cut=0
> I get the usual list of errors and then the vecotr map is created.

I don't understand. What are those errors? Copy/paste please.

> then
> g.remove vect=dem_isoipse_050
> g.region res=1
> r.contour input=elevation.dem@PERMANENT output=dem_isoipse_050 step=50 cut=0
> I get a program abnormal end (killed) at:
> 
> Reading data.
> Percent complete: Killed

Is it using all your memory and swap before then? I couldn't reproduce your
particular case with "Percent complete: Killed", but my machine freezes when
I
run r.contour on a "too big" DEM.

Could you find settings to reproduce the error in the Spearfish dataset?

Devs,

Is r.contour reading the whole DEM into memory? It looks so.

> using the r.contour GUI, I noticed that selecting the "suppress single
> crossing error messages" (this and only this) kills both the gui and the
> d.m (as well as gis.m).

For this Cedric and Michael could maybe tell?  As well as for some your other
recent posts regarding GUI issues.

Thanks.

Maciek
Mon, Apr 10 2006 11:11:45    Mail sent by giorgio.agugiaro@unipd.it  
Return-Path <giorgio.agugiaro@unipd.it>
Delivered-To grass-bugs@lists.intevation.de
From "Giorgio Agugiaro" <giorgio.agugiaro@unipd.it>
To "Maciek Sieczka via RT" <grass-bugs@intevation.de>
Subject R: [bug #4269] (grass) problems with r.contour
Date Mon, 10 Apr 2006 11:11:47 +0200
Message-ID <KLEGKAGGLKLDJPCFGMDOCEIFCAAA.giorgio.agugiaro@unipd.it>
MIME-Version 1.0
Content-Type text/plain; charset="iso-8859-1"
Content-Transfer-Encoding 7bit
X-Priority 3 (Normal)
X-MSMail-Priority Normal
X-Mailer Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
X-MimeOLE Produced By Microsoft MimeOLE V6.00.2900.2670
In-Reply-To <20060410084755.3740B101F00@lists.intevation.de>
Importance Normal
X-PMX-Version 5.1.0.207369, Antispam-Engine: 2.1.0.0, Antispam-Data: 2006.4.10.15509
X-Spam-Status No, hits=-4.9 tagged_above=-999.0 required=3.0 tests=BAYES_00
X-Spam-Level
ciao!

[...]

> > r.contour input=elevation.dem@PERMANENT output=dem_isoipse_050
> step=50 cut=0
> > I get the usual list of errors and then the vecotr map is created.
>
> I don't understand. What are those errors? Copy/paste please.

sorry, I was meaning the "normal" error messages "single crossing error
messages", whose output can be deselected via "suppress single crossing
error messages".

> > then
> > g.remove vect=dem_isoipse_050
> > g.region res=1
> > r.contour input=elevation.dem@PERMANENT output=dem_isoipse_050
> step=50 cut=0
> > I get a program abnormal end (killed) at:
> >
> > Reading data.
> > Percent complete: Killed
>
> Is it using all your memory and swap before then? I couldn't
> reproduce your
> particular case with "Percent complete: Killed", but my machine
> freezes when I
> run r.contour on a "too big" DEM.
>
> Could you find settings to reproduce the error in the Spearfish dataset?
>

this was my guess too (but just a guess ;-)
to reproduce it in spearfish:

g.region rast=elevation.dem@PERMANENT (standard res should be 30)
g.region res=1
r.contour input=elevation.dem@PERMANENT output=dem_isoipse_050 step=50 cut=0
Thanks for your quick answer!
Ciao!

giorgio


Comment | Reply | Take | Resolve

You are currently authenticated as guest.
[Show Configuration] [Login as another user]

Users Guide - Mail Commands - Homepage of RequestTracker 1.0.7 - list any request