Re: [GRASS-dev] Grass7 GUI compilation failed
I can confirm that - I don't think it was the animation, I think it was the g.gui.* that started to break down modules for me. I am still on 10.6.8 but I am trying to set up a machine with 10.8 for testing. Currently, the compilation ends with error for the following modules: /Users/helena/grassdev7/grass_trunk/gui/wxpython/animation /Users/helena/grassdev7/grass_trunk/gui/wxpython/mapswipe /Users/helena/grassdev7/grass_trunk/gui/wxpython/gmodeler /Users/helena/grassdev7/grass_trunk/gui/wxpython/rlisetup /Users/helena/grassdev7/grass_trunk/gui/wxpython/psmap /Users/helena/grassdev7/grass_trunk/gui/wxpython/dbmgr /Users/helena/grassdev7/grass_trunk/gui/wxpython/vdigit /Users/helena/grassdev7/grass_trunk/gui/wxpython/iclass but it affects more than the modules above - for example switching to 3d view is broken - it has erratic behavior (I can provide more details - there are too many to list here but the following error shows up pythonw2.6[69774] : CGContextRestoreGState: invalid context 0x0 (this is just with a single DEM, no volumes) v.digit runs but hangs on rendering mapswipe works fine except for the manual page which gives CGContextRestoreGState: invalid context 0x0 animation tool does not start at all giving the following error CGBitmapContextCreate: invalid data bytes/row: should be at least 4 for 8 integer bits/component, 3 componen ts, kCGImageAlphaNoneSkipFirst. pythonw2.6[69774] : CGContextTranslateCTM: invalid context 0x0 pythonw2.6[69774] : CGContextScaleCTM: invalid context 0x0 Note that this issue is different from GRASS6.4.3 crashing gui on OS X 10.7 and 10.8 when drawing isosurfaces - that works OK on 10.6 but the issues above are in GRASS7 only and on Mac OSX 10.6 - 10.8 Helena On Dec 29, 2012, at 3:57 PM, Michael Barton wrote: > This has been broken since the introduction of the animation module and > apparently now is affecting other modules that used to compile fine. So GRASS > 7 is increasingly broken for the Mac. Volume displays have been broken for > many months now. If someone could tell me what has changed with the > introduction of these new modules and related changes to the other ones, I > might be able to find out what is breaking on the Mac. I'm guessing that it > is a new class that calls some wxPython windowing routine that has a problem, > but I don't know what it is. > > Michael > > C. Michael Barton > Director, Center for Social Dynamics & Complexity > Professor of Anthropology, School of Human Evolution & Social Change > Arizona State University > > voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC) > fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC) > www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu > > > > > > > > > > > > On Dec 29, 2012, at 1:00 PM, > wrote: > >> From: Rashad M >> Subject: Re: [GRASS-dev] Grass7 GUI compilation failed >> Date: December 29, 2012 11:25:17 AM MST >> To: >> >> >> here is output from v.digit >> make >> ml >> make[6]: Entering directory `/code/grass/grass70/gui/wxpython/vdigit' >> GISRC=/code/grass/grass70/dist.x86_64-unknown-linux-gnu/demolocation/.grassrc70 >> GISBASE=/code/grass/grass70/dist.x86_64-unknown-linux-gnu >> PATH="/code/grass/grass70/dist.x86_64-unknown-linux-gnu/bin:/code/grass/grass70/dist.x86_64-unknown-linux-gnu/bin:$PATH" >> >> PYTHONPATH="/code/grass/grass70/dist.x86_64-unknown-linux-gnu/etc/python:/code/grass/grass70/dist.x86_64-unknown-linux-gnu/etc/python:$PYTHONPATH" >> >> LD_LIBRARY_PATH="/code/grass/grass70/dist.x86_64-unknown-linux-gnu/bin:/code/grass/grass70/dist.x86_64-unknown-linux-gnu/lib:/code/grass/grass70/dist.x86_64-unknown-linux-gnu/lib:" >> LC_ALL=C >> /code/grass/grass70/dist.x86_64-unknown-linux-gnu/scripts/g.gui.vdigit >> --html-description < /dev/null | grep -v '\|' > >> g.gui.vdigit.tmp.html >> Traceback (most recent call last): >> File >> "/code/grass/grass70/dist.x86_64-unknown-linux-gnu/scripts/g.gui.vdigit", >> line 39, in >> import wx >> ImportError: No module named wx >> make[6]: *** [g.gui.vdigit.tmp.html] Error 1 >> rm g.gui.vdigit.tmp.html >> make[6]: Leaving directory `/code/grass/grass70/gui/wxpython/vdigit' >> make[5]: *** [guiscript] Error 2 >> >> >> On Sat, Dec 29, 2012 at 9:57 PM, Rashad M wrote: >> grass7.0 fails compilation at first and continues only after setting >> PYTHONPATH. >> >> This becomes a routine for recompilation. Is there any work around to >> automatically pickup wxPython? >> >> Here is my error log: >> >> Started compilation: Sat Dec 29 21:46:17 IST 2012 >> -- >> Errors in: >> /code/grass/grass70/gui/wxpython/animation >> /code/grass/grass70/gui/wxpython/mapswipe >> /code/grass/grass70/gui/wxpython/gmodeler >> /code/grass/grass70/gui/wxpython/rlisetup >> /code/grass/grass70/gui/wxpython/psmap >> /code/grass/grass70/gui/wxpython/dbmgr >> /code/grass/grass70/gui/wxpython/vdigit >> -- >> In case of errors please change into the directory with error and ru
Re: [GRASS-dev] [GRASS GIS] #1801: r3.in.ascii fails in GRASS6.4.3
#1801: r3.in.ascii fails in GRASS6.4.3
--+-
Reporter: helena| Owner: grass-dev@…
Type: defect| Status: new
Priority: critical | Milestone: 6.4.3
Component: Raster3D | Version: svn-releasebranch64
Keywords: r3.in.ascii, raster3d import |Platform: MacOSX
Cpu: OSX/Intel |
--+-
Comment(by helena):
I found that r3.in.ascii fails when there is nulls exported as * in the
ascii file
GRASS 6.4.3svn (nc_spm_05):~/grassdata/indata/test3d > r3.in.ascii
hatelevnull3d.asci out=test3d_importfpnull
Loading data ... (484x654x10)
ERROR: asciiToG3d: read failed
if I replace * with 0 it reads the file OK
GRASS 6.4.3svn (nc_spm_05):~/grassdata/indata/test3d > r3.in.ascii
hatelev_test3d.asci out=test3d_importfp0
Loading data ... (484x654x10)
r3.in.ascii complete.
but as mentioned above, the initialization of the parameters has bugs, for
example, if I try to define null as *
(which is the default for r3.out.ascii) I get error
GRASS 6.4.3svn (nc_spm_05):~/grassdata/indata/test3d > r3.in.ascii
hatelevnull3d.asci out=test3d_importfpnull nv=* --o
ERROR: getParams: NULL-value value invalid
(nv="*" does not help)
perhaps because it expects number instead of string in main.c ?
param.nv = G_define_option();
param.nv->key = "nv";
param.nv->type = TYPE_STRING;
param.nv->required = NO;
param.nv->multiple = NO;
param.nv->answer = "none";
param.nv->description =
_("String representing NULL value data cell (use 'none' if no such
value)");
}
/*---*/
static void
getParams(char **input, char **output, int *convertNull, double
*nullValue)
{
*input = param.input->answer;
*output = param.output->answer;
*convertNull = (strcmp(param.nv->answer, "none") != 0);
if (*convertNull)
if (sscanf(param.nv->answer, "%lf", nullValue) != 1)
fatalError("getParams: NULL-value value invalid");
G_debug(3, "getParams: input: %s, output: %s", *input, *output);
}
The default,default issue seems to be indeed in g3dparam.c -for example,
I think the answer should be float instead of default here:
param->type->answer = "default";
param->type->options = "default,double,float";
param->type->description = _("Data type used in the output file");
It is supposed to get value described in G3D Defaults, but it does not.
--
Ticket URL:
GRASS GIS
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] grass 6.4.3 release plan (open issues)
(back to http://trac.osgeo.org/grass/wiki/Grass6Planning#GRASS6.4.3 ) On Mon, Mar 5, 2012 at 5:36 PM, Markus Metz wrote: > On 3/5/12, Martin Landa wrote: >> 2012/3/5 Markus Neteler : ... > All differences between the GRASS 6 and GRASS 7 version of > v.vect.stats are only related to API changes in GRASS 7. > > The module has been tested for some time, by different users by now, > it is IMHO safe to include it in 6.4.3. The module does amongst other > things a PIP (points in polygon) count, a feature frequently > requested. Unfortunately we omitted so far to move v.vect.stats from Addons into core GRASS 6 - should this happen now? Any problems with that? Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Grass7 GUI compilation failed
This has been broken since the introduction of the animation module and apparently now is affecting other modules that used to compile fine. So GRASS 7 is increasingly broken for the Mac. Volume displays have been broken for many months now. If someone could tell me what has changed with the introduction of these new modules and related changes to the other ones, I might be able to find out what is breaking on the Mac. I'm guessing that it is a new class that calls some wxPython windowing routine that has a problem, but I don't know what it is. Michael C. Michael Barton Director, Center for Social Dynamics & Complexity Professor of Anthropology, School of Human Evolution & Social Change Arizona State University voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC) fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC) www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu On Dec 29, 2012, at 1:00 PM, mailto:grass-dev-requ...@lists.osgeo.org>> wrote: From: Rashad M mailto:mohammedrasha...@gmail.com>> Subject: Re: [GRASS-dev] Grass7 GUI compilation failed Date: December 29, 2012 11:25:17 AM MST To: mailto:grass-dev@lists.osgeo.org>> here is output from v.digit make ml make[6]: Entering directory `/code/grass/grass70/gui/wxpython/vdigit' GISRC=/code/grass/grass70/dist.x86_64-unknown-linux-gnu/demolocation/.grassrc70 GISBASE=/code/grass/grass70/dist.x86_64-unknown-linux-gnu PATH="/code/grass/grass70/dist.x86_64-unknown-linux-gnu/bin:/code/grass/grass70/dist.x86_64-unknown-linux-gnu/bin:$PATH" PYTHONPATH="/code/grass/grass70/dist.x86_64-unknown-linux-gnu/etc/python:/code/grass/grass70/dist.x86_64-unknown-linux-gnu/etc/python:$PYTHONPATH" LD_LIBRARY_PATH="/code/grass/grass70/dist.x86_64-unknown-linux-gnu/bin:/code/grass/grass70/dist.x86_64-unknown-linux-gnu/lib:/code/grass/grass70/dist.x86_64-unknown-linux-gnu/lib:" LC_ALL=C /code/grass/grass70/dist.x86_64-unknown-linux-gnu/scripts/g.gui.vdigit --html-description < /dev/null | grep -v '\|' > g.gui.vdigit.tmp.html Traceback (most recent call last): File "/code/grass/grass70/dist.x86_64-unknown-linux-gnu/scripts/g.gui.vdigit", line 39, in import wx ImportError: No module named wx make[6]: *** [g.gui.vdigit.tmp.html] Error 1 rm g.gui.vdigit.tmp.html make[6]: Leaving directory `/code/grass/grass70/gui/wxpython/vdigit' make[5]: *** [guiscript] Error 2 On Sat, Dec 29, 2012 at 9:57 PM, Rashad M mailto:mohammedrasha...@gmail.com>> wrote: grass7.0 fails compilation at first and continues only after setting PYTHONPATH. This becomes a routine for recompilation. Is there any work around to automatically pickup wxPython? Here is my error log: Started compilation: Sat Dec 29 21:46:17 IST 2012 -- Errors in: /code/grass/grass70/gui/wxpython/animation /code/grass/grass70/gui/wxpython/mapswipe /code/grass/grass70/gui/wxpython/gmodeler /code/grass/grass70/gui/wxpython/rlisetup /code/grass/grass70/gui/wxpython/psmap /code/grass/grass70/gui/wxpython/dbmgr /code/grass/grass70/gui/wxpython/vdigit -- In case of errors please change into the directory with error and run 'make'. If you get multiple errors, you need to deal with them in the order they appear in the error log. If you get an error building a library, you will also get errors from anything which uses the library. -- Finished compilation: Sat Dec 29 21:53:10 IST 2012 wxpython is installed from ubuntu repos. so its in the default path -- Regards, Rashad -- Regards, Rashad ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS Vector Support
2012/12/29 Brian Sanjeewa Rupasinghe : > As Martin requested will you be able to update gdal-grass osgeo4W package? > If not, i will be > able to do it provided you support me because i do not have any experience > in creating packages. I didn't request anything. I just said that I had no time at this moment to update this package. If you send me updated package I will happily upload it to the osgeo4w framework (having permission for that as a maintainer of grass and grassXX-dev packages). Martin -- Martin Landa * http://geo.fsv.cvut.cz/~landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS Vector Support
Hi, 2012/12/29 Jürgen E. : > And you are positive that the GDAL plugin would help? The above description > sounds like a more general problem and I don't see any connection to the > missing plugin at all. > > Does GRASS itself need the GDAL GRASS plugin at all? no, GRASS doesn't not need GDAL compiled with GRASS support. No GRASS module depends on it. Otherwise we would maintain gdal-grass plugin for OSGeo4W. Anyway it would be good idea to maintain it, personally I could find time for that later, but not now. Martin -- Martin Landa * http://geo.fsv.cvut.cz/~landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Grass7 GUI compilation failed
here is output from v.digit make ml make[6]: Entering directory `/code/grass/grass70/gui/wxpython/vdigit' GISRC=/code/grass/grass70/dist.x86_64-unknown-linux-gnu/demolocation/.grassrc70 GISBASE=/code/grass/grass70/dist.x86_64-unknown-linux-gnu PATH="/code/grass/grass70/dist.x86_64-unknown-linux-gnu/bin:/code/grass/grass70/dist.x86_64-unknown-linux-gnu/bin:$PATH" PYTHONPATH="/code/grass/grass70/dist.x86_64-unknown-linux-gnu/etc/python:/code/grass/grass70/dist.x86_64-unknown-linux-gnu/etc/python:$PYTHONPATH" LD_LIBRARY_PATH="/code/grass/grass70/dist.x86_64-unknown-linux-gnu/bin:/code/grass/grass70/dist.x86_64-unknown-linux-gnu/lib:/code/grass/grass70/dist.x86_64-unknown-linux-gnu/lib:" LC_ALL=C /code/grass/grass70/dist.x86_64-unknown-linux-gnu/scripts/g.gui.vdigit --html-description < /dev/null | grep -v '\|' > g.gui.vdigit.tmp.html Traceback (most recent call last): File "/code/grass/grass70/dist.x86_64-unknown-linux-gnu/scripts/g.gui.vdigit", line 39, in import wx ImportError: No module named wx make[6]: *** [g.gui.vdigit.tmp.html] Error 1 rm g.gui.vdigit.tmp.html make[6]: Leaving directory `/code/grass/grass70/gui/wxpython/vdigit' make[5]: *** [guiscript] Error 2 On Sat, Dec 29, 2012 at 9:57 PM, Rashad M wrote: > grass7.0 fails compilation at first and continues only after setting > PYTHONPATH. > > This becomes a routine for recompilation. Is there any work around to > automatically pickup wxPython? > > Here is my error log: > > Started compilation: Sat Dec 29 21:46:17 IST 2012 > -- > Errors in: > /code/grass/grass70/gui/wxpython/animation > /code/grass/grass70/gui/wxpython/mapswipe > /code/grass/grass70/gui/wxpython/gmodeler > /code/grass/grass70/gui/wxpython/rlisetup > /code/grass/grass70/gui/wxpython/psmap > /code/grass/grass70/gui/wxpython/dbmgr > /code/grass/grass70/gui/wxpython/vdigit > -- > In case of errors please change into the directory with error and run > 'make'. > If you get multiple errors, you need to deal with them in the order they > appear in the error log. If you get an error building a library, you will > also get errors from anything which uses the library. > -- > Finished compilation: Sat Dec 29 21:53:10 IST 2012 > > > wxpython is installed from ubuntu repos. so its in the default path > > > -- > Regards, >Rashad > -- Regards, Rashad ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS Vector Support
Hi Brian, On Sat, 29. Dec 2012 at 10:58:19 +0530, Brian Sanjeewa Rupasinghe wrote: > I need to automate some GRASS functions in my research work. If there is a > possibility to build gdal_grass plugin for Windows it is highly > appreciated. Even the Python scripts that call GRASS functions from > outside for MS_Windows do not connect with GRASS even though the > instructions provided in the GRASS wiki is followed. I have posted this > problem in grass-windows forum and finally advised me to bring the problem > down to grass-dev list. And you are positive that the GDAL plugin would help? The above description sounds like a more general problem and I don't see any connection to the missing plugin at all. Does GRASS itself need the GDAL GRASS plugin at all? Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13Fax. +49-4931-918175-50 Software Engineer D-26506 Norden http://www.norbit.de committ(ed|ing) to Quantum GIS IRC: jef on FreeNode -- norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH Rheinstrasse 13, 26506 Norden GF: Jelto Buurman, HR: Amtsgericht Emden, HRB 5502 ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] Grass7 GUI compilation failed
grass7.0 fails compilation at first and continues only after setting PYTHONPATH. This becomes a routine for recompilation. Is there any work around to automatically pickup wxPython? Here is my error log: Started compilation: Sat Dec 29 21:46:17 IST 2012 -- Errors in: /code/grass/grass70/gui/wxpython/animation /code/grass/grass70/gui/wxpython/mapswipe /code/grass/grass70/gui/wxpython/gmodeler /code/grass/grass70/gui/wxpython/rlisetup /code/grass/grass70/gui/wxpython/psmap /code/grass/grass70/gui/wxpython/dbmgr /code/grass/grass70/gui/wxpython/vdigit -- In case of errors please change into the directory with error and run 'make'. If you get multiple errors, you need to deal with them in the order they appear in the error log. If you get an error building a library, you will also get errors from anything which uses the library. -- Finished compilation: Sat Dec 29 21:53:10 IST 2012 wxpython is installed from ubuntu repos. so its in the default path -- Regards, Rashad ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS Vector Support
Hi Markus, As Martin requested will you be able to update gdal-grass osgeo4W package? If not, i will be able to do it provided you support me because i do not have any experience in creating packages. On Sat, Dec 29, 2012 at 4:19 PM, Martin Landa wrote: > Hi, > > 2012/12/29 Brian Sanjeewa Rupasinghe : > >> Martin Landa took over GRASS maintenance in OSGeo4W - maybe he has more > >> interest in building the plugin... > > I put it to my TODO list. Unfortunately there are many other things > which are more urgent. Sorry. Is there anyone in grass-dev ML who is > interested to update gdal-grass osgeo4w package? Then I will happily > uploaded to the osgeo4w framework. > > Martin > > -- > Martin Landa * http://geo.fsv.cvut.cz/~landa > ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS Vector Support
Hi, 2012/12/29 Brian Sanjeewa Rupasinghe : >> Martin Landa took over GRASS maintenance in OSGeo4W - maybe he has more >> interest in building the plugin... I put it to my TODO list. Unfortunately there are many other things which are more urgent. Sorry. Is there anyone in grass-dev ML who is interested to update gdal-grass osgeo4w package? Then I will happily uploaded to the osgeo4w framework. Martin -- Martin Landa * http://geo.fsv.cvut.cz/~landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] List of new features in GRASS 7: please update
OK, those links may not be pretty, but that is a minor issue if compared to the convenience of having those links there. So I would certainly keep them. What are the plans for the Wiki vs trac? I see some articles are marked to be moved to trac (like the GRASS 7 ideas collection). What is supposed to go where (Wiki or Trac), Wiki for end-user relevant information, Trac for information more relevant for developers? I can see some advantages in such a system, but there are bound to be cases where information is relevant for both developers and users. One example is the NewFeatures page. Especially the part about changes in libraries is mostly interesting for developers. However, all the module changes and new modules are highly relevant for the users (I guess there must be a lot of GRASS 7 users by now). All in all, it seems to make sense to me to move the GRASS 7 ideas collection to Trac, and move the 'http://trac.osgeo.org/grass/wiki/Grass7/NewFeatures' to the Wiki, or alternatively, give it an easy to find link on the front page of the Wiki (replace the link to GRASS 7 ideas collection in the Development box on the Wiki front page with a link to New Features perhaps). Cheers On Fri 28 Dec 2012 10:38:08 PM CET, Markus Neteler wrote: On Fri, Dec 28, 2012 at 2:46 PM, Paulo van Breugel wrote: Nice work Markus! Thanks but it is joint work :) I am not very good in catchy intro words, but I would mention the number of new modules (44+ vector, grass and image modules + general, GUI, etc modules) and some key improvements / enhancements of existing modules (like the very significant speed improvements in vector handling)? Yes, definitely. I guess the links are made with some kind of alias? Would it be possible to not show the 'G7:' as part of all links? I would be more than pleased but trac has no clue about reasonable links. We can simply take it out again, if too ugly. Or move the page to Mediawiki. Opinions? One question about bash the scripts. it is mentioned that all bash scrips are converted to Python. Yes. Especially for portability reasons and speed. Perhaps obvious, but these concerns the scripts that are part of the GRASS installation. One can still use external bash scripts (and hopefully that will remain the case). Yes sure. For example, most scripts available in the grass 6 add-on repository can be used in grass 7, albeit sometimes some adaptations are needed because of syntax changes) Sure - users are welcome to continue like that. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
