and to really confuse matters a bunch, I first decreased the -tilesizex and -tilesizey from 1024 to 256, and then increased it to 2048 to run some timing tests. The last run completed! For reference, the command is as follows:
otbcli_LSMSSegmentation -in /tmp/Brandt3_stip/WV02_20130220110706_103001001F6BB100_13FEB20110706-P1BS-500423517010_01_P002_filtered_range.tif -inpos /tmp/Brandt3_stip/WV02_20130220110706_103001001F6BB100_13FEB20110706-P1BS-500423517010_01_P002_filtered_spat.tif -out /tmp/Brandt3_stip/WV02_20130220110706_103001001F6BB100_13FEB20110706-P1BS-500423517010_01_P002_seg.tif uint32 -ranger 30 -spatialr 5 -minsize 0 -tilesizex 2048 -tilesizey 2048 -tmpdir /tmp/Brandt3_tmp -cleanup 0 Because this error was triggered, and then cleared, by setting the tilesizex and -tilesizey size, I think I would consider this a bug and not an undocumented feature. -- -- Check the OTB FAQ at http://www.orfeo-toolbox.org/FAQ.html You received this message because you are subscribed to the Google Groups "otb-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/otb-users?hl=en --- You received this message because you are subscribed to the Google Groups "otb-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
