I can't register with osgeo to submit a bug as no-one has replied with a 'mantra' for me to do so... what a convoluted bug reporting system!
And in your opinion Moritz, does it look like my workflow will not be possible unless I find a 64bit machine with a decent amount of RAM? Thanks for your support on this. James On 27 October 2016 at 20:47, Moritz Lennert <[email protected]> wrote: > Le Thu, 27 Oct 2016 20:33:23 +0100, > James Duffy <[email protected]> a écrit : > > > On 27 October 2016 at 17:48, Moritz Lennert > > <[email protected]> wrote: > > > > > > > Running: > > > > > > > > r.univar -et gp_ortho.1 zones=gp_seg_optimum_clump > > > > output=testoutput2.csv > > > > > > > > Returns: > > > > > > > > Current region rows: 12627, cols: 23991 > > > > ERROR: G_realloc: unable to allocate 224000 bytes of memory at > > > > raster/r.univar/r.univar_main.c:324 > > > > > > > > > Ok, so the issue is with r.univar (although the issue has made me > > > aware that i.segment.stats could be made way more memory efficient > > > as well). > > > > > > How much RAM do you have on your machine ? > > > > > > > It's a virtual machine which I have dedicated about 10GB. > > > > > > > > > > This warrants a bug report. Would you be willing to file one on > > > http://trac.osgeo.org/grass ? > > > > > > > I'm happy to submit it if you can guide me as to what exactly should > > go into it please? > > > > The bug report should concentrate on r.univar > > You should provide: > > - region settings (output of g.region -p) > - info about the two maps going into the command, i.e. r.info, plus the > info that the segment map is an output of r.clump and thus > sequentially numbered > - the error message > > I don't know how difficult it will be to allow for lower memory usage > in r.univar, so we'll have to see if an improvement is possible. > > Moritz > > -- *James Duffy* PhD Researcher Environment and Sustainability Institute Penryn Campus University of Exeter Penryn Cornwall TR10 9FE
_______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
