[GRASS-user] Recommendations for v.surf.rst parameters for huge region

2020-10-16 Thread Eric Patton
Hello list, I am trying to interpolate raster values for a single massive dataset that represents dozens of multibeam bathymetry surveys over a few decades. The region is pretty big: all of Eastern Canada; at 100m resolution there are ~ 464M cells. The raster data has a wide range of completen

Re: [GRASS-user] v.random segfault

2020-10-16 Thread Eric Patton
On 20/10/16 12:10PM, Maris Nartiss wrote: > > Hello Eric, > it is hard to say if I hit your bug or another one, but I managed to > reproduce crash and already reported it to the bug tracker: > https://github.com/OSGeo/grass/issues/1024 > > The problem seems to be with specifying parameter "restri

Re: [GRASS-user] r.param.scale issue

2020-10-16 Thread Vincent Bain
Your remarks Māris are very interesting. I am actually having trouble with my CPU (AMD Ryzen 7 3800X) and debian stable: I should try to test several debian backports to have the full temperature sensors support (not yet supported with 4.19) but am not especially at ease with these quite dodgy mani

Re: [GRASS-user] r.param.scale issue

2020-10-16 Thread Markus Neteler
Vincent, On Thu, Oct 15, 2020 at 6:39 PM Vincent Bain wrote: > > Markus, Māris, and others who feel concerned, > > following on with this post, I am wondering if either something is > wrong with my openMP install (then it's not the place to bother anyone > with it) or if there may be something wr

Re: [GRASS-user] v.random segfault

2020-10-16 Thread Maris Nartiss
Hello Eric, it is hard to say if I hit your bug or another one, but I managed to reproduce crash and already reported it to the bug tracker: https://github.com/OSGeo/grass/issues/1024 The problem seems to be with specifying parameter "restrict". If you really need it, just wait for a fix as it sho

Re: [GRASS-user] r.param.scale issue

2020-10-16 Thread Maris Nartiss
Valgrind leak check is needed only for developers as it tracks memory consumption not its errors (although in this case it allowed to notice OpenMP presence by shear luck). As your valgrind run is clean, this is a dead end. On my system I also have a OpenMP and pthreads configuration. Unfortunatel