Details Ticket 3613


Comment | Reply | Take | Resolve


Serial Number 3613
Subject g.region vect=frame: bottom of the vector not visible
Area grass6
Queue grass
Requestors tutey@o2.pl
Owner none
Status open
Last User Contact Tue Sep 13 07:21:00 2005 (3 yr ago)
Current Priority 30
Final Priority 70
Due No date assigned
Last Action Mon Apr 9 15:08:08 2007 (1 yr ago)
Created Wed Sep 7 13:45:12 2005 (3 yr ago)

Transaction History Ticket 3613


Wed, Sep 7 2005 13:45:12    Request created by guest  
Subject: g.region vect=frame: bottom part of the 

Platform: GNU/Linux/i386
grass obtained from: CVS
grass binary for platform: Compiled from Sources
GRASS Version: cvs 07.09.2005

I can't see the bottom of my vector "frame" although I should, as I used "g.region
vect=frame":

http://www.biol.uni.wroc.pl/sieczka/udostepnione/gregion/g.region_vect.png

Surprisingly, I have to subsequently run "g.region s=s-96" in order to see my
whole "frame":

http://www.biol.uni.wroc.pl/sieczka/udostepnione/gregion/g.region_vect_s.png
What's that? I've been having this problem with any vector file, this one is
only an example. This bug has been present since Grass 5.7. I'm using a Grass
default x monitor window size here.

My "frame" for testing:
http://www.biol.uni.wroc.pl/sieczka/udostepnione/gregion/frame.tar.bz2

My projection and region info (after "g.region vect=frame") if they matter:
GRASS 6.1.cvs (caves_utm33):~ > g.proj -p
-PROJ_INFO-------------------------------------------------
name       : Universe Transverse Mercator
proj       : utm
datum      : wgs84
a          : 6378137
es         : 0.0066943800
zone       : 33
no_defs    : defined
-PROJ_UNITS------------------------------------------------
unit       : metre
units      : metres
meters     : 1


GRASS 6.1.cvs (caves_utm33):~ > g.region vect=frame; g.region -p
projection: 1 (UTM)
zone:       33
datum:      wgs84
ellipsoid:  a=6378137 es=0.00669438
north:      5740300
south:      5649044
west:       563572
east:       634168
nsres:      1
ewres:      1
rows:       91256
cols:       70596
Wed, Sep 7 2005 13:47:02    Subject changed to g.region vect=frame: bottom of the vector not visible by msieczka  
Thu, Sep 8 2005 02:48:20    Mail sent by hamish_nospam@yahoo.com  
Return-Path <hamish_nospam@yahoo.com>
Delivered-To grass-bugs@lists.intevation.de
Date Thu, 8 Sep 2005 12:48:02 +1200
From Hamish <hamish_nospam@yahoo.com>
To Request Tracker <grass-bugs@intevation.de>
Cc grass5@grass.itc.it
Subject Re: [GRASS5] [bug #3613] (grass) g.region vect=frame: bottom part of the
Message-Id <20050908124802.77383943.hamish_nospam@yahoo.com>
In-Reply-To <20050907114512.B0E4B1006D7@lists.intevation.de>
References <20050907114512.B0E4B1006D7@lists.intevation.de>
X-Mailer Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-pc-linux-gnu)
X-Face M<EoB)"*Z~u!,vFhXmw}R_KbdBta*P_=T|rbBL'e1/CQ9;/1g\BU3&!=y8ria$2Uk!HT&BB 8i?|X_+7~1jsy}F~g$2va%3fV`*=L(*cem[@3\yg,G,@rg6/QMJ
Mime-Version 1.0
Content-Type text/plain; charset=US-ASCII
Content-Transfer-Encoding 7bit
X-Spam-Status No, hits=-4.0 tagged_above=-999.0 required=3.0 tests=BAYES_00, FORGED_YAHOO_RCVD
X-Spam-Level
> this bug's URL: http://intevation.de/rt/webrt?serial_num=3613
> ---------------------------------------------------------------------
> 
> Subject: g.region vect=frame: bottom part of the 
> 
> Platform: GNU/Linux/i386
> grass obtained from: CVS
> grass binary for platform: Compiled from Sources
> GRASS Version: cvs 07.09.2005
> 
> I can't see the bottom of my vector "frame" although I should, as I
> used "g.region vect=frame":
> 
> http://www.biol.uni.wroc.pl/sieczka/udostepnione/gregion/g.region_vect.png
> 
> Surprisingly, I have to subsequently run "g.region s=s-96" in order to
> see my whole "frame":
> 
> http://www.biol.uni.wroc.pl/sieczka/udostepnione/gregion/g.region_vect_s.png
> 
> What's that? I've been having this problem with any vector file, this
> one is only an example. This bug has been present since Grass 5.7. I'm
> using a Grass default x monitor window size here.

If you resize the display monitor does it fix itself? If so, probably an
off-by-one error due to casting a double to an int without adding 0.5 to
take care of rounding. (it just chops off the decimal place)

There were a few of these that Glynn (& partly myself) fixed a long long
time ago, it is likely more remain (e.g. in d.barscale, d.rast.edit).

I am not surprised at all to see this, glad you have found a work
around.

also try splitting the screen up into four equal quadrants with d.frame
and see what happens.



Hamish


Mon, Sep 12 2005 15:21:53    Mail sent by msieczka  
Hamish wrote:

> If you resize the display monitor does it fix itself?

No. No matter how hard I punish my mouse, the bottom part is never displayed.
Unless I narrow my monitor enough to have upper and lower margins. But until
magins don't appear the bottom of my "frame" vector is not visible.

> also try splitting the screen up into four equal quadrants with
> d.frame and see what happens.

I cannot get d.frame to work for me. Eg.:

GRASS 6.1.cvs (caves_utm33):~ > d.frame at=0,0,50,50
<at=0,0,50,50> invalid request

Any hints?

I used d.split however and there is something else strange going on, see:
https://intevation.de/rt/webrt?serial_num=3628&display=History

Maciek
Tue, Sep 13 2005 07:21:00    Mail sent by hamish_nospam@yahoo.com  
Return-Path <hamish_nospam@yahoo.com>
Delivered-To grass-bugs@lists.intevation.de
Date Tue, 13 Sep 2005 17:20:43 +1200
From Hamish <hamish_nospam@yahoo.com>
To Maciek Sieczka via RT <grass-bugs@intevation.de>
Cc grass5@grass.itc.it
Subject Re: [bug #3613] (grass) g.region vect=frame: bottom of the vector not visible
Message-Id <20050913172043.280674e9.hamish_nospam@yahoo.com>
In-Reply-To <20050912132154.021451006DC@lists.intevation.de>
References <20050912132154.021451006DC@lists.intevation.de>
X-Mailer Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-pc-linux-gnu)
X-Face M<EoB)"*Z~u!,vFhXmw}R_KbdBta*P_=T|rbBL'e1/CQ9;/1g\BU3&!=y8ria$2Uk!HT&BB 8i?|X_+7~1jsy}F~g$2va%3fV`*=L(*cem[@3\yg,G,@rg6/QMJ
Mime-Version 1.0
Content-Type text/plain; charset=US-ASCII
Content-Transfer-Encoding 7bit
X-Spam-Status No, hits=-4.0 tagged_above=-999.0 required=3.0 tests=BAYES_00, FORGED_YAHOO_RCVD
X-Spam-Level
> I cannot get d.frame to work for me. Eg.:
> 
> GRASS 6.1.cvs (caves_utm33):~ > d.frame at=0,0,50,50
> <at=0,0,50,50> invalid request


Usage:
 d.frame [-cepslD] [frame=name] [at=bottom,top,left,right]

(full usage wasn't given in man pages or GUI until recently)


try

d.frame at=0,50,0,50



d.split did this:

#  split it: left (win1) and right (win2)
        d.frame -e
        d.frame -c frame=win1  at=0,100,0,49
        d.frame -c frame=win2  at=0,100,50,100
or
#  split it: top (win1) and bottom (win2)
        d.frame -e
        d.frame -c frame=win1  at=50,100,0,100
        d.frame -c frame=win2  at=0,49,0,100


100-50 != 49-0, so the left or bottom panel is slightly smaller than its
partner, allowing the one frame to be slightly zoomed vs the other.

The split should be 0->49.5 and 50.5->100; now fixed in CVS. (bug #3628)


these two commands should give some hints as to this bug (#3613):
d.frame -D
d.info -r

Using xmag on the new version shows that things are better, but still
maybe off a little bit, more obvious as you strech the window bigger.

In fact doing:
v.in.region test_box
export GRASS_WIDTH=1000
export GRASS_HEIGHT=800
d.mon x1
d.split cmd1="d.vect test_box" cmd2="d.vect test_box"

and then using the mouse to drag the left/right side of the window to
resize & redraw highlights the bug -> after 3-5 resizings the right
panel grows at the expense of the left one. (Vertical resizing doesn't
make a difference in this view=vert case)

And when using d.split view=horiz and resizing in the vertical you
see the same thing happen too (but not by resizing in the horizontal).

Again I'd blame a truncation cast vs. correct rounding in the C code.



Hamish


Wed, Jul 26 2006 14:52:14    User changed to tutey@o2.pl by msieczka  
Mon, Apr 9 2007 15:08:08    Comments added by msieczka  
Regarding the main v.in.region+d.vect issue, Glynn has recently thorougly
explained why this is not a bug [1] and cannot be "fixed" without introducing
other problems.

However, the issue remains, and might a source of confussion for users. Thus
I'm leaving it open.

[1]http://grass.itc.it/pipermail/grass-dev/2007-April/030216.html

Maciek
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