Thanks Anna, I believe you are correct with your ideas, unfortunately the only fix given is way beyond my level of understanding and coding and from what I gather uses a non svn version python 4.1. There was a mention in that link to a newer version of python 4.0.8 but it seems it has not either been implemented or if it has uploaded to the repository.
Evidently the bug is in both python 3.9 and the 4.0 version currently used in the repository. Is there likely to be an updated version loaded to repository before too long that corrects the problem? Kind regards Tim Dr Timothy Glyn Southern > On 11 Apr 2021, at 04:55, Anna Petrášová <[email protected]> wrote: > > Hello, > > On Sat, Apr 10, 2021 at 12:51 PM Timothy Glyn Southern via grass-user > <[email protected] <mailto:[email protected]>> wrote: > Problem with wxpython guy in Manjaro with grass 7.8.5 > > Dear colleagues, > > Following a period of low use due to health issues I am once again trying to > use GRASS to visualise and analyse archaeological data. > > I am running Manjaro and the latest download of GRASS from AUR. > > It starts fine and shows both display windows for the GUI and then the > windows crash. It is repeatable. > > I have tried removing GRASS and reinstalling but that has not fixed the > issue. As well I have tried changing the flags on the GUI. None make any > difference, as soon as the mouse is apparently moved the windows crash. > > Is this a known problem and is there a work around? > > based on your description it sounds like a bug in wxPython with Python 3.9: > https://github.com/OSGeo/grass/issues/1123 > <https://github.com/OSGeo/grass/issues/1123> > > Hope that helps, > Anna > > > Thanks > > Tim Southern > Dr Timothy Glyn Southern > 0155 941 8432 > 0791 076 6814 > > > > > >> On 4 Apr 2021, at 20:00, [email protected] >> <mailto:[email protected]> wrote: >> >> Send grass-user mailing list submissions to >> [email protected] <mailto:[email protected]> >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://lists.osgeo.org/mailman/listinfo/grass-user >> <https://lists.osgeo.org/mailman/listinfo/grass-user> >> or, via email, send a message with subject or body 'help' to >> [email protected] >> <mailto:[email protected]> >> >> You can reach the person managing the list at >> [email protected] >> <mailto:[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. Re: r.watershed identify inland watershed (ming han) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Sat, 3 Apr 2021 16:23:26 -0400 >> From: ming han <[email protected] <mailto:[email protected]>> >> To: Micha Silver <[email protected] <mailto:[email protected]>> >> Cc: GRASS user list <[email protected] >> <mailto:[email protected]>> >> Subject: Re: [GRASS-user] r.watershed identify inland watershed >> Message-ID: >> <cad+uawjx1xbcc6jk+hau8mnda7ceajfweeeyewq379efwrp...@mail.gmail.com >> <mailto:cad%2buawjx1xbcc6jk%[email protected]>> >> Content-Type: text/plain; charset="utf-8" >> >> Hi Micha >> >> I understand what you mean. But it requires another step to >> manually identify depressions from these pre-conditioned DEM. >> >> Cheers >> Ming >> >> >> Micha Silver <[email protected] <mailto:[email protected]>> ?2021?4?3??? >> ??12:43??? >> >>> >>> On 4/2/21 5:37 PM, ming han wrote: >>>> Maybe I am the only one who has this demand. Following is just a >>>> recommendation to GRASS r.watershed function. >>>> Maybe it is worth having an option to avoid r.watershed overcome >>>> depressions. >>>> The reasons are 1) there are many hydrologically pre condition DEM >>>> data available globally, such as:HydroSHEDS, MERIT >>>> 2) the depression in these DEM are real >>>> depressions, overcome these depressions will make the entire drainage >>>> system >>> >>> >>> Regarding Hydrosheds, the documentation[1] in section 3.4 explains how >>> they overcame the problem of sinks. They performed a regular "fill >>> sinks" operation on areas that were SRTM artifacts. True natural >>> depressions were identified manually, then another manual procedure of >>> carving rivers was done to force flow thru these depressions and produce >>> hydrologically correct streams and basins. So pre-conditioning to >>> overcome depressions is not a magic bullet... >>> >>> >>> In my opinion, the best results are obtained when true depressions >>> (pits, salt playas or karst regions) are identified, and set to NULL in >>> the elevation raster. That will allow r.watershed to stop routing at >>> those locations, and produce correct stream and basin layers. >>> >>> >>> [1]https://hydrosheds.org/images/inpages/HydroSHEDS_TechDoc_v1_2.pdf >>> <https://hydrosheds.org/images/inpages/HydroSHEDS_TechDoc_v1_2.pdf> >>> >>> >>>> incorrectly. >>>> >>>> I understand GRASS has other functions to solve this problem, but just >>>> a user recommendation. I use GRASS a lot. >>>> >>>> Thanks >>>> Ming >>>> >>>> ming han <[email protected] <mailto:[email protected]> >>>> <mailto:[email protected] <mailto:[email protected]>>> >>>> ?2021?3?30??? ??8:06??? >>>> >>>> Got it, thanks everyone~ >>>> Ming >>>> >>>> Micha Silver <[email protected] <mailto:[email protected]> >>>> <mailto:[email protected] <mailto:[email protected]>>> >>>> ?2021?3?29??? ??2:40??? >>>> >>>> Hello: >>>> >>>> You might try `r.param.scale`, or even better `r.geomorphons` >>>> modules to >>>> identify geomorphology features, then filter out all pixels >>>> identified >>>> as pits. >>>> >>>> >>>> r.watershed is purposely designed to overcome depressions, and >>>> find flow >>>> routing thru these spots. So I don't think you can use that >>>> module to >>>> identify depressions. >>>> >>>> >>>> On 3/27/21 8:49 PM, ming han wrote: >>>>> Hi Everyone >>>>> >>>>> When I do watershed delineation using r.watershed for >>>> great salt >>>>> lake watershed. I found r.watershed always tried to assign >>>> an outlet >>>>> for a great salt lake, which does actually not exist because >>>> it is an >>>>> inland lake and the great salt lake has no watershed outlet >>>> at all. >>>>> >>>>> I noticed that there is a depression option. But is >>>> there any >>>>> way that r.watershed can automatically identify depressions >>>> while >>>>> defining flow accumulation and stream network? >>>>> >>>>> Thanks >>>>> Ming >>>>> >>>>> _______________________________________________ >>>>> grass-user mailing list >>>>> [email protected] <mailto:[email protected]> >>>>> <mailto:[email protected] <mailto:[email protected]>> >>>>> https://lists.osgeo.org/mailman/listinfo/grass-user >>>>> <https://lists.osgeo.org/mailman/listinfo/grass-user> >>>> <https://lists.osgeo.org/mailman/listinfo/grass-user >>>> <https://lists.osgeo.org/mailman/listinfo/grass-user>> >>>> >>>> -- >>>> Micha Silver >>>> Ben Gurion Univ. >>>> Sde Boker, Remote Sensing Lab >>>> cell: +972-523-665918 >>>> >>> -- >>> Micha Silver >>> Ben Gurion Univ. >>> Sde Boker, Remote Sensing Lab >>> cell: +972-523-665918 >>> >>> >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: >> <http://lists.osgeo.org/pipermail/grass-user/attachments/20210403/6b22a457/attachment-0001.html >> >> <http://lists.osgeo.org/pipermail/grass-user/attachments/20210403/6b22a457/attachment-0001.html>> >> >> ------------------------------ >> >> Subject: Digest Footer >> >> _______________________________________________ >> grass-user mailing list >> [email protected] <mailto:[email protected]> >> https://lists.osgeo.org/mailman/listinfo/grass-user >> <https://lists.osgeo.org/mailman/listinfo/grass-user> >> >> >> ------------------------------ >> >> End of grass-user Digest, Vol 180, Issue 4 >> ****************************************** > > _______________________________________________ > grass-user mailing list > [email protected] <mailto:[email protected]> > https://lists.osgeo.org/mailman/listinfo/grass-user > <https://lists.osgeo.org/mailman/listinfo/grass-user>
_______________________________________________ grass-user mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/grass-user
