On Mon, Jul 15, 2013 at 10:04 AM, Moritz Lennert <mlenn...@club.worldonline.be> wrote: > On Fri, July 12, 2013 21:59, Markus Metz wrote: >> On Fri, Jul 12, 2013 at 4:36 PM, Moritz Lennert >> <mlenn...@club.worldonline.be> wrote: >>> Proxmox(Openvz) container running Debian testing, 200GB disk space, 10GB >>> RAM, 4 i7 CPUs >>> >>>> g.region -p >>> projection: 1 (UTM) >>> zone: 33 >>> datum: wgs84 >>> ellipsoid: wgs84 >>> north: 4876400 >>> south: 4849792 >>> west: 610056 >>> east: 634648 >>> nsres: 0.5 >>> ewres: 0.5 >>> rows: 53216 >>> cols: 49184 >>> cells: 2617375744 >>> >>>> r.univar 2013_04_24_orthorectified_mosaic_PAN_img02 >>> 100% >>> total null and non-null cells: 2617375744 >>> total null cells: 2061647833 >>> >>> Of the non-null cells: >>> ---------------------- >>> n: 555727911 >>> >>>> i.group -l pan_r_ir >>> group <pan_r_ir> references the following raster maps >>> ------------- >>> <2013_04_24_orthorectified_mosaic_PAN_img02@PERMANENT> >>> <2013_04_24_orthorectified_mosaic_XS_img02.5@PERMANENT> >>> <2013_04_24_orthorectified_mosaic_XS_img02.7@PERMANENT> >>> >>> >>>> time i.segment -w group=pan_r_ir out=seg_weighted_pan_r_ir >>>> threshold=0.01 >>>> memory=8192 >>> Loading input bands... >>> Pass 1: >>> ERROR: Invalid region id 0 >> >> Please try r57074. >
> I still get exactly the same error. Anything I can do to debug ? You will need to add loops that go through the segment ids and check if any id is set to zero. Another possibility is that the region growing algorithm does not find a best neighbor for a given region, which it should. There should always be a valid best neighbor. I can prepare a patch for you with additional debug tests, hopefully until this afternoon, then you could have a chance to start the module again before you go offline. Markus M > > Moritz > > P.S. I'll be offline between this afternoon and Thursday morning. > _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
