Re: [GRASS-dev] GSoC Ideas
f user cancels the wizard, just fine. Let him enjoy the demo project and display first time screen also on the next startup iff there is no project with data in the GISDBASE. This would not interfere with a big, fat warning if someone tries to import external data into sample projects (NC, Spearfish, ...) or any other enhancements that could be done. Huh, I think I answered most of points from previous emails (except going into details of potential architecture (thus Anna for wxPython expertise) or user friendliness (thus Vero)). Thank you to everyone who read this far and sorry for all unintentional fuss I caused. Probably Linda you are right – it is too ambitious for an experimental project that might get tossed away at the end. I see that Anna has already removed the idea from the wiki, most likely for good. Do not restore it, let it be so. We can return to this idea at any point later if we feel need for it. I have plenty to do to fix pointer juggling bugs in the new module I have almost finished (anisotropic smoothing). Māris. piektd., 2024. g. 16. febr., plkst. 10:41 — lietotājs Linda Kladivová () rakstīja: > > Hello Māris, > > just to add some other info, we did several surveys among GRASS users about > first-time user experience with Anna, Martin and Vashek and we also tested > old and new startup mechanisms in a real environment within the usability > testing - you can have a look at our article: > https://www.mdpi.com/2220-9964/12/9/376. > > As Anna has already written, the results of usability testing were indeed > mixed but I would like to emphasize one thing - most of the usability > participants (first-time users) said to me that they simply expect they will > be directly redirected to the main software window where they can start > working without knowing anything about the software. The current "info bar" > solution goes in that direction and although I have to admit that it has > flaws there are ways how to make it better and Anna has already written some > points. > > I think it would be nice to focus on how to make the current solution better > (it is definitely doable and even desirable) and not go back to some > alternatives to the old solution. > Above that, it would be extremely time-consuming to implement any dialog > wizards and at the same time the impact of that "dialog" solution is very > uncertain - one important thing we also learned from surveys and discussions > inside/outside the community is that the one good generally acceptable > solution simply does not exist here - it will always be a compromise. > > Just my two cents. :-) > Linda > > -- Původní e-mail -- > Od: Maris Nartiss via grass-dev > Komu: Anna Petrášová , Veronica Andreo > > Kopie: GRASS-dev > Datum: 15. 2. 2024 13:04:24 > Předmět: Re: [GRASS-dev] GSoC Ideas > > Hello Anna, Vero. > I added the welcome screen idea we discussed during our Prague > meeting. I think it would be a good GSOC project as it is quite easy > and at the same time will allow to understand if it is the way to go. > Anna, would you be able to be a co-mentor as it is a GUI project? Or > who else could be? > Vero, your user-centric view also would be valuable. > Please edit the wiki accordingly. > > Thanks, > Māris. > > sestd., 2024. g. 3. febr., plkst. 06:34 — lietotājs Anna Petrášová via > grass-dev () rakstīja: > > > > Hi, > > > > I created a GSoC Ideas 2024 page on grasswiki (as opposed to trac wiki, > > which I think we should be moving away from): > > https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024 > > > > It's not updated yet, I plan to add more topics. If you want to mentor a > > topic, we can discuss it here. > > > > Anna > > ___ > > grass-dev mailing list > > grass-dev@lists.osgeo.org > > https://lists.osgeo.org/mailman/listinfo/grass-dev > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GSoC Ideas
Hello Anna, Vero. I added the welcome screen idea we discussed during our Prague meeting. I think it would be a good GSOC project as it is quite easy and at the same time will allow to understand if it is the way to go. Anna, would you be able to be a co-mentor as it is a GUI project? Or who else could be? Vero, your user-centric view also would be valuable. Please edit the wiki accordingly. Thanks, Māris. sestd., 2024. g. 3. febr., plkst. 06:34 — lietotājs Anna Petrášová via grass-dev () rakstīja: > > Hi, > > I created a GSoC Ideas 2024 page on grasswiki (as opposed to trac wiki, which > I think we should be moving away from): > https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024 > > It's not updated yet, I plan to add more topics. If you want to mentor a > topic, we can discuss it here. > > Anna > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GRASS Windows issues
Windows issues are hard to debug as most of developers are on Linux boxes. Do you have an ArcGIS install by any chance? In the past ArcGIS was a source of different problems for GRASS as it would register its Python globally and then GRASS would pick wrong Python version resulting myriad of strange errors. M. svētd., 2023. g. 10. dec., plkst. 17:25 — lietotājs Gandalf the Gray via grass-dev () rakstīja: > > Hi Jeff > > Thanks for the link. I installed the 8.4 dev version. and it gives exactly > the same error as with GRASS standalone from grass,osgeo.org, GRASS installed > with OSGeo4W, and from the QGIS standalone installer. > > I am now suspecting that it might not be the wxpython included in the > installers, but my pc itself. > > Regards > > Pieter > > On Sun, Dec 10, 2023 at 2:52 PM Jeff McKenna via grass-dev > wrote: >> >> Hi Pieter, >> >> I personally always recommend using WinGRASS, it is very reliable. >> (thanks to MartinL) https://wingrass.fsv.cvut.cz/grass84/ >> >> Merry Christmas to you and the GRASS GIS family, >> >> -jeff >> >> >> >> -- >> Jeff McKenna >> GatewayGeo: Developers of MS4W, & offering MapServer Consulting/Dev >> co-founder of FOSS4G >> http://gatewaygeo.com/ >> >> >> >> On 2023-12-09 12:17 a.m., Gandalf the Gray via grass-dev wrote: >> > Hi guys. >> > >> > In desperation I am posting to this list. I have posted on the OSGeo4W >> > list a week ago to no avail. >> > >> > I hope someone can help me. >> > >> > On a clean install of OSGeo4W (and for that matter standalone QGIS and >> > GRASS installers), I get the following error (see attached screenshot) >> > starting any version of GRASS. >> > >> > On GRASS 7, I can do a mapset selection before crash, but the other 2 >> > just crashes. >> > >> > Install is on a machine that ran GRASS up until a week ago, until I >> > uninstalled the OSGeo4W stack, and deleted everything. There is nothing >> > strange about my Windows Setup >> > >> > I hope anyone can help me, and I hope you can see the screenshot. >> > >> > Regards >> > >> > Pieter >> > >> > _ >> >> ___ >> grass-dev mailing list >> grass-dev@lists.osgeo.org >> https://lists.osgeo.org/mailman/listinfo/grass-dev > > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] Bugs in i.cca module
Thanks, Markus. I managed to compile version before the ccmath library in a VM. I managed to get results with steps from that e-mail. But as soon as I try to repeat the steps after the ccmath introduction commit, I get a segfault. With my fix, there is no segfault but the results are nan when the original version gives some numbers. Thus although my PR would eliminate a segfault, it does not fix i.cca. I'm not certain if it is worth to merge as segfault at least is a clear sign that something is really wrong :D Unless someone can look into the code to see what's wrong with it, I'd say we disable compilation of i.cca and remove it from the GUI menu. Māris. trešd., 2023. g. 15. nov., plkst. 11:50 — lietotājs Markus Neteler () rakstīja: > > Hi Māris, all, > > On Wed, Nov 15, 2023 at 8:35 AM Maris Nartiss via grass-dev > wrote: > > > > Hello devs, > > Just playing around I decided to run i.cca module. Seems that it has > > been broken since 2009(!) (there is a bug report from 2014 in Trac > > [1]). I managed to fix the segfault [2] but it left me with a > > different problem – the module runs just fine but produces NULLs as an > > output. This boils down to at one point trying to calculate sqrt from > > negative numbers. I am not that familiar with the CCA algorithm > > implemented in the module and thus have no idea if it is a bug in the > > code or just bad input data. > > > > I hope somebody can help me to sort this out or provide a working example, > > Māris. > > Digging in my inbox I found this thread from 2009: > https://lists.osgeo.org/pipermail/grass-dev/2009-August/045656.html > > It contains some discussion and examples. Maybe not much of a help but > a kind of pointer. > > Markus > > > 1. https://trac.osgeo.org/grass/ticket/2297 > > 2. https://github.com/OSGeo/grass/pull/3239 > > ___ > > grass-dev mailing list > > grass-dev@lists.osgeo.org > > https://lists.osgeo.org/mailman/listinfo/grass-dev > > -- > Markus Neteler, PhD > https://www.mundialis.de - free data with free software > https://grass.osgeo.org > https://neteler.org/blog ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] Bugs in i.cca module
Hello devs, Just playing around I decided to run i.cca module. Seems that it has been broken since 2009(!) (there is a bug report from 2014 in Trac [1]). I managed to fix the segfault [2] but it left me with a different problem – the module runs just fine but produces NULLs as an output. This boils down to at one point trying to calculate sqrt from negative numbers. I am not that familiar with the CCA algorithm implemented in the module and thus have no idea if it is a bug in the code or just bad input data. I hope somebody can help me to sort this out or provide a working example, Māris. 1. https://trac.osgeo.org/grass/ticket/2297 2. https://github.com/OSGeo/grass/pull/3239 ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [EXTERNAL] [release planning] GRASS GIS 8.3.1
If I read the log file correctly, the actual error message is: /usr/bin/install: cannot create regular file '/builddir/build/BUILD/grass-8.3.1/dist.x86_64-redhat-linux-gnu/docs/html/raster3d_layout.png': File exists make[3]: *** [../../include/Make/HtmlRules.make:14: /builddir/build/BUILD/grass-8.3.1/dist.x86_64-redhat-linux-gnu/docs/html/raster3d_layout.png] Error 1 Could it be related to the fact that we ship three(!) copies of this file? Maris. piektd., 2023. g. 27. okt., plkst. 13:32 — lietotājs Markus Neteler via grass-dev () rakstīja: > > Dear all, > I am trying to build G8.3.1 for Fedora (F40) but get a strange error: > > GRASS GIS 8.3.1 exported compilation log > -- > Started compilation: Thu Oct 26 12:52:40 UTC 2023 > -- > Errors in: > /builddir/build/BUILD/grass-8.3.1/raster3d/r3.in.ascii > > Related to > gcc x86_64 13.2.1-4.fc40 > ? > > The log is here, help quite welcome: > https://kojipkgs.fedoraproject.org//work/tasks/2196/108132196/build.log > > Thanks, > Markus > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
