Re: [GRASS-dev] 6.4.0 blocker bugs
Hi, 2010/8/18 Helena Mitasova hmit...@unity.ncsu.edu: as Hamish has noted the choice of the default GUI is decided by whoever does the binary package (?). the default (or initial) GUI is set in init.sh [1]. The packager can include rc file to overwrite the settings. My suggestion is to change the default GUI directly in init.sh. Changing this variable between 6.4.0 and 6.4.1 seems to big quite big change when considering releasing policy. Martin [1] http://trac.osgeo.org/grass/browser/grass/branches/releasebranch_6_4/lib/init/init.sh#L28 -- Martin Landa landa.martin gmail.com * http://gama.fsv.cvut.cz/~landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] 6.4.0 blocker bugs
On Mon, Aug 23, 2010 at 5:07 PM, Martin Landa landa.mar...@gmail.com wrote: 2010/8/18 Helena Mitasova hmit...@unity.ncsu.edu: ... My suggestion is to change the default GUI directly in init.sh. Changing this variable between 6.4.0 and 6.4.1 seems to big quite big change when considering releasing policy. Additionally it is a pain to prepare tutorial - you don't want to replicate everything with then quickly outdating screenshots for Mac + Linux users when a new GUI is there and already default on winGRASS... On Wed, Aug 18, 2010 at 5:26 AM, Hamish hamis...@yahoo.com wrote: ... Finally, for the FOSS4G 2010 OSGeo Live GIS disc I have packaged it with ~/.grassrc6 containing GRASS_GUI=wxpython, so there Linux starts with the wxGUI. At this point we should do it for the rest of the users, too. I'd really like to avoid to be flooded with messages of where is the new GUI?? content since the standard Linux distros will package whatever is set in the software. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] r.watershed failing: seg fault and exit code 35584
Hi folks, I have a quick troubleshooting question. I'm trying to run r.watershed to extract stream segments and I'm receiving the following error; GRASS 6.4.0RC5+39438 (ccarleton.minanha.utm):~ r.watershed elevation=aster_srtm_dem_fil...@cloudremoval threshold=10 stream=aster_srtm_stream memory=300 SECTION 1a (of 5): Initiating Memory. SECTION 1b (of 5): Determining Offmap Flow. 100% SECTION 2: A * Search. 100% SECTION 3: Accumulating Surface Flow. 100% SECTION 4: Watershed determination. Segmentation fault WARNING: Subprocess failed with exit code 35584 WARNING: category information for [aster_srtm_stream] in [geophys] missing or invalid I haven't been able to find something in the mailing lists about this, but if you know of somewhere that I can find a solution I'd appreciate the link. I'm running GRASS 6.4 RC5 on Ubuntu LTS 10.04 with a Dell Precision T7500 Workstation. The region settings are as follows; projection: 1 (UTM) zone: 16 datum: wgs84 ellipsoid: wgs84 north: 1942292.77488498 south: 1798172.56898554 west: 174812.49733566 east: 382055.4579663 nsres: 15.2143 ewres: 15.00021429 rows: 9608 cols: 13816 cells: 132744128 The actual DEM is much smaller than this (a composite ASTER/SRTM DEM) and I have 12GB of memory so I'd be surprised if this was a memory problem. Before I start working with GDB or other in-depth debugging I was hoping someone would have a short answer for this already. Thanks for your time, Chris ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] 6.4.0 blocker bugs
[...] On Wed, Aug 18, 2010 at 5:26 AM, Hamish [hamish_b at yahoo.com] wrote: ... Finally, for the FOSS4G 2010 OSGeo Live GIS disc I have packaged it with ~/.grassrc6 containing GRASS_GUI=wxpython, so there Linux starts with the wxGUI. At this point we should do it for the rest of the users, too. I'd really like to avoid to be flooded with messages of where is the new GUI?? content since the standard Linux distros will package whatever is set in the software. Markus there was so much effort to create a new and working gui (wxgui) which will be the next generation user interface. IMHO this should be honored a lot and the wxgui should be considered as the default in the upcoming grass64-release, mainly to get feedback and being able to improve this interface. on windows - I've played a lot with grass64/65/70-versions - I've almost never used the tcltk-gui. so I vote for wxgui as the default for all os-platforms. best regards Helmut ___ Neu: WEB.DE De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: https://produkte.web.de/go/demail02 smime.p7s Description: S/MIME Cryptographic Signature ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
