Dear All, Grass 6.4 has completed a third automatic update this week! However it still fails when trying to run the wxpython GU1
Following the last upgrade this morning attempting to run the Wxpthyon GUI returns File”/opt/grass/etc/wxpython/wxgui.py”, line 34, in <module> from lmgr.frame import GMFrame File “/opt/grass/etc/wxpython/lmgr/frame.py", line 46, in <module> from lmgr.layertree import LayerTree, UNIcons File “/opt/grass/etc/wxpython/lmgr/layertree.py", line 37, in <module> from mapdisp.frame import MapFrame File “opt/grass/etc/wxpython/mapdisp/frame.py”, line 52, in <module> from wxplot.profile import ProfileFrame File “opt/grass/etc/wxpython/wxplot/profile.py”, line 23, in <module> import wx.lib.plot as plot File ‘usr/lib/python2.7/site-packages/wx-2.8gtk2-unicode/wx/lib/plot.py” line 132 in <module> raise ImportError, “Numeric, numarray or numPy not found. \n. + msg ImportError: Numeric, numarray or NumPy not found. This module requires the Numeric/numarray or NumPy module, which could not be imported. It probably is not installed(it’s not part of the standard Python distribution). See the Numeric Python site (http://numpy.scipy.org <http://numpy.scipy.org/>) for information on downloading source or binaries. Doing a Find on python returns the following /etc/apparmour.d/abstractions/python /usr/share/doc/packages/python /usr/share/gdb/python /usr/share/bash-completion/completion/python /usr/share/kde4/apps/kconversion/scripting_support/python /usr/lib/gimp/2.0/python /usr/lib/libreoffice/share/scripts/python usr/lib/python /usr/bin/python /opt/grass/etc/python Doing a find on NumPy /usr/lib/python2.7/site-packages/numpy /usr/lib/python2.7/site-packages/numpy/core/include/numpy Can anyone help get GRASS back up and running? Thanks Tim Southern 17, Park Close, Sonning Common, Oxfordshire RG4 9RY > On 14 Nov 2014, at 14:05, [email protected] wrote: > > Send grass-user mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.osgeo.org/mailman/listinfo/grass-user > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of grass-user digest..." > > > Today's Topics: > > 1. FW:11/14/2014 2:34:02 AM 4 (Rebecca Stedham) > 2. Re: Problem with r.basin in grass7 (Helmut Kudrnovsky) > 3. Re: d.out.file / d.save - Shell-script use issues (Glynn Clements) > 4. Re: A question before I embark on a programming exercise > (Glynn Clements) > 5. Re: A question before I embark on a programming exercise > (Rainer M Krug) > 6. Re: A question before I embark on a programming exercise > (Moritz Lennert) > 7. Re: d.out.file / d.save - Shell-script use issues > (Nikos Alexandris) > 8. Re: d.out.file / d.save - Shell-script use issues (Peter L?we) > 9. Re: A question before I embark on a programming exercise > (Thomas Adams) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 14 Nov 2014 02:34:02 +0000 > From: "Rebecca Stedham" <[email protected]> > To: "hazel smith" <[email protected]>, "gv1978" > <[email protected]>, "grass user request" > <[email protected]>, "grass user" > <[email protected]>, "hr" <[email protected]>, "hcpickard" > <[email protected]>, "Hertha Taverner Wood" <[email protected]> > Subject: [GRASS-user] FW:11/14/2014 2:34:02 AM 4 > Message-ID: <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > http://www.sansebastianradio.com/sqgruarc/rkemiqdhspxdpdqqqiphr.pvywnulkxerfsnggv > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Rebecca Stedham > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://lists.osgeo.org/pipermail/grass-user/attachments/20141114/5118f922/attachment-0001.html> > > ------------------------------ > > Message: 2 > Date: Fri, 14 Nov 2014 01:02:26 -0800 (PST) > From: Helmut Kudrnovsky <[email protected]> > To: [email protected] > Subject: Re: [GRASS-user] Problem with r.basin in grass7 > Message-ID: <[email protected]> > Content-Type: text/plain; charset=us-ascii > > Andrea Timmermann wrote >> and got: >> >> Downloading precompiled GRASS Addons <r.stream.distance>... >> Traceback (most recent call last): >> File "C:\Program Files (x86)\GRASS GIS >> 7.1.svn/scripts/g.extension.py", line 1083, in <module> >> sys.exit(main()) >> File "C:\Program Files (x86)\GRASS GIS >> 7.1.svn/scripts/g.extension.py", line 1071, in main >> install_extension(xmlurl) >> File "C:\Program Files (x86)\GRASS GIS >> 7.1.svn/scripts/g.extension.py", line 479, in >> install_extension >> ret += install_extension_win(module) >> File "C:\Program Files (x86)\GRASS GIS >> 7.1.svn/scripts/g.extension.py", line 709, in >> install_extension_win >> zfobj = zipfile.ZipFile(fo) >> File "C:\Program Files (x86)\GRASS GIS >> 7.1.svn\Python27\lib\zipfile.py", line 766, in __init__ >> self._RealGetContents() >> File "C:\Program Files (x86)\GRASS GIS >> 7.1.svn\Python27\lib\zipfile.py", line 807, in >> _RealGetContents >> raise BadZipfile, "File is not a zip file" >> zipfile.BadZipfile: File is not a zip file > > the r.stream.* addons are now back again for winGRASS, see e.g. > http://wingrass.fsv.cvut.cz/grass71/addons/grass-7.1.svn/ > > thanks to Martin. > > > > ----- > best regards > Helmut > -- > View this message in context: > http://osgeo-org.1560.x6.nabble.com/Problem-with-r-basin-in-grass7-tp5169155p5172960.html > Sent from the Grass - Users mailing list archive at Nabble.com. > > > ------------------------------ > > Message: 3 > Date: Fri, 14 Nov 2014 09:31:37 +0000 > From: Glynn Clements <[email protected]> > To: Vaclav Petras <[email protected]> > Cc: GRASS user list <[email protected]>, Peter Löwe > <[email protected]> > Subject: Re: [GRASS-user] d.out.file / d.save - Shell-script use > issues > Message-ID: <[email protected]> > Content-Type: text/plain; charset=us-ascii > > > Vaclav Petras wrote: > >> I kindly ask command line users of d.* commands, especially those using d.* >> commands in scripts, to test and participate in discussions concerning d.* >> commands in GRASS GIS 7. For example, d.out.file was added (relatively) >> lately to 7 and there is new command d.to.rast. They are designed to work >> with wxGUI (including wx monitors). > > Could you choose a different prefix for these commands, and leave d.* > for display commands? > > -- > Glynn Clements <[email protected]> > > > ------------------------------ > > Message: 4 > Date: Fri, 14 Nov 2014 09:40:35 +0000 > From: Glynn Clements <[email protected]> > To: Moritz Lennert <[email protected]> > Cc: "[email protected]" <[email protected]> > Subject: Re: [GRASS-user] A question before I embark on a programming > exercise > Message-ID: <[email protected]> > Content-Type: text/plain; charset=us-ascii > > > Moritz Lennert wrote: > >> r.mapcalc down_id = if(dir=1, id[1,1], if(dir=2, id[0,1], if(dir=3, >> id[-1,1] .... etc > > r.mapcalc follows C expression syntax; "="is assignment, "==" is the > equality test. > > -- > Glynn Clements <[email protected]> > > > ------------------------------ > > Message: 5 > Date: Fri, 14 Nov 2014 11:21:15 +0100 > From: Rainer M Krug <[email protected]> > To: Glynn Clements <[email protected]> > Cc: "[email protected]" <[email protected]> > Subject: Re: [GRASS-user] A question before I embark on a programming > exercise > Message-ID: <[email protected]> > Content-Type: text/plain; charset="us-ascii" > > Glynn Clements <[email protected]> writes: > >> Moritz Lennert wrote: >> >>> r.mapcalc down_id = if(dir=1, id[1,1], if(dir=2, id[0,1], if(dir=3, >>> id[-1,1] .... etc >> >> r.mapcalc follows C expression syntax; "="is assignment, "==" is the >> equality test. > > In this case shouldn't it be > > ,---- > | r.mapcalc down_id = if(dir==1, id[1,1], if(dir==2, id[0,1], if(dir==3, > id[-1,1] .... etc > `---- > > with "==" after the dir? > > Rainer > > -- > Rainer M. Krug > email: Rainer<at>krugs<dot>de > PGP: 0x0F52F982 > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 494 bytes > Desc: not available > URL: > <http://lists.osgeo.org/pipermail/grass-user/attachments/20141114/b1be3185/attachment-0001.pgp> > > ------------------------------ > > Message: 6 > Date: Fri, 14 Nov 2014 12:36:20 +0100 > From: Moritz Lennert <[email protected]> > To: Rainer M Krug <[email protected]>, Glynn Clements > <[email protected]> > Cc: "[email protected]" <[email protected]> > Subject: Re: [GRASS-user] A question before I embark on a programming > exercise > Message-ID: <[email protected]> > Content-Type: text/plain; charset=windows-1252; format=flowed > > On 14/11/14 11:21, Rainer M Krug wrote: >> Glynn Clements <[email protected]> writes: >> >>> Moritz Lennert wrote: >>> >>>> r.mapcalc down_id = if(dir=1, id[1,1], if(dir=2, id[0,1], if(dir=3, >>>> id[-1,1] .... etc >>> >>> r.mapcalc follows C expression syntax; "="is assignment, "==" is the >>> equality test. >> >> In this case shouldn't it be >> >> ,---- >> | r.mapcalc down_id = if(dir==1, id[1,1], if(dir==2, id[0,1], if(dir==3, >> id[-1,1] .... etc >> `---- >> >> with "==" after the dir? > > Yes, that's what Glynn is saying. Sorry, I wrote this example too quickly. > > Moritz > > > ------------------------------ > > Message: 7 > Date: Fri, 14 Nov 2014 14:07:08 +0200 > From: Nikos Alexandris <[email protected]> > To: Vaclav Petras <[email protected]> > Cc: GRASS user list <[email protected]>, Peter L?we > <[email protected]> > Subject: Re: [GRASS-user] d.out.file / d.save - Shell-script use > issues > Message-ID: <20141114120708.GA11735@tpx1c2g> > Content-Type: text/plain; charset=us-ascii > > * Vaclav Petras <[email protected]> [2014-11-12 09:35:32 -0500]: > >> I kindly ask command line users of d.* commands, especially those using d.* >> commands in scripts, to test and participate in discussions concerning d.* >> commands in GRASS GIS 7. For example, d.out.file was added (relatively) >> lately to 7 and there is new command d.to.rast. They are designed to work >> with wxGUI (including wx monitors). > > I quickly ran through most d.* commands (except for the d.vect* stuff). > Some notes: > > d.erase: I would like to do `d.erase black`. Black is a *good* > background color. > > d.info -g: Maybe change the -g's flag description? 's/geographic//' to > avoid confusion(s) (geographic vs. projected, etc.)? > > d.rast.edit: let instructions/mouse actions explained inside a > wx-monitor? > > For the d.what* commands, the icons to perform such queries exist > already in a wx-Monitor, right? > > Isn't it possible to merge d.out.file and d.to.rast? Maybe instruct > "to.rast" with a flag or an explicit output name? > > Nikos > > > ------------------------------ > > Message: 8 > Date: Fri, 14 Nov 2014 13:45:59 +0100 > From: "Peter L?we" <[email protected]> > To: "Nikos Alexandris" <[email protected]> > Cc: GRASS user list <[email protected]> > Subject: Re: [GRASS-user] d.out.file / d.save - Shell-script use > issues > Message-ID: > > <trinity-337e5b41-f6ee-4f8d-9991-3b7d0ec2781a-1415969159733@3capp-gmx-bs37> > > Content-Type: text/plain; charset=UTF-8 > > Hi Nikos, dear all, > >> >> Isn't it possible to merge d.out.file and d.to.rast? Maybe instruct >> "to.rast" with a flag or an explicit output name? >> >> Nikos >> > I strongly support this. The cumbersome re-import of the monitor content to > use as a raster layer (d.to.file -> r.in.gdal -> r.composite) could be > avoided. > > Peter > > > > > ------------------------------ > > Message: 9 > Date: Fri, 14 Nov 2014 07:05:41 -0700 > From: Thomas Adams <[email protected]> > To: Rainer M Krug <[email protected]> > Cc: "[email protected]" <[email protected]>, Glynn > Clements <[email protected]> > Subject: Re: [GRASS-user] A question before I embark on a programming > exercise > Message-ID: > <CAGxgkWhNqc_ho7yqagQ5etTp6Um2H9ZHxLH=qoy3w8y4t7d...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Glynn & Rainer, > > YES, absolutely -- I caught that and made it '==' instead of '='. When > typing quickly, I sometimes make that mistake and then have to correct > myself. But fundamentally, Moritz' approach worked very well and produced > what I needed. I have a more difficult problem now, something I think I can > only resolve by using higher resolution data. But, that is OK, too, because > I should get better modeling results in the end. I'm trying to create my > own approach to generating the file, that when used by the model, gives > essentially the same results. > > The folks who wrote the model and software to generate this runoff/flow > connectivity file between pixels, found that with coarser pixel > resolutions, the connection between pixels was badly distorted, in > physically unreasonable ways. I don't have their original code, so I can > not use it, plus, I really want to model at much finer spatial resolutions > anyway, where the problem should go vanish. > > So, I just need to use higher resolution DEM data, which I have, rather > than trying to do things at the default 4km resolution. > > One question I have: it would be very nice to be able to show how the > pixels are connected using vectors, essentially the drainage network. Any > thoughts how to do this? > > Regards, > Tom > > On Fri, Nov 14, 2014 at 3:21 AM, Rainer M Krug <[email protected]> wrote: > >> Glynn Clements <[email protected]> writes: >> >>> Moritz Lennert wrote: >>> >>>> r.mapcalc down_id = if(dir=1, id[1,1], if(dir=2, id[0,1], if(dir=3, >>>> id[-1,1] .... etc >>> >>> r.mapcalc follows C expression syntax; "="is assignment, "==" is the >>> equality test. >> >> In this case shouldn't it be >> >> ,---- >> | r.mapcalc down_id = if(dir==1, id[1,1], if(dir==2, id[0,1], if(dir==3, >> id[-1,1] .... etc >> `---- >> >> with "==" after the dir? >> >> Rainer >> >> -- >> Rainer M. Krug >> email: Rainer<at>krugs<dot>de >> PGP: 0x0F52F982 >> >> _______________________________________________ >> grass-user mailing list >> [email protected] >> http://lists.osgeo.org/mailman/listinfo/grass-user >> > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://lists.osgeo.org/pipermail/grass-user/attachments/20141114/ab2e2770/attachment.html> > > ------------------------------ > > _______________________________________________ > grass-user mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/grass-user > > End of grass-user Digest, Vol 103, Issue 23 > *******************************************
_______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
