[GRASS-dev] how difficult would it be to modify i.edge to not load the entire image into memory ?
markus.metz.giswork at gmail.com
Thu Dec 14 03:44:46 PST 2017
On Thu, Dec 14, 2017 at 11:47 AM, Moritz Lennert <
mlennert at club.worldonline.be> wrote:
> On 14/12/17 05:45, Vaclav Petras wrote:
>> Hi Moritz,
>> I'm currently at AGU
> Enjoy ! :-)
>> and can't dig into the code, but yes, I think it can be rewritten with
segment library, preferably with MarkusM's "segment or in-memory" wrapper.
> Great ! Markus, is this wrapper in the library, or just in existing
modules ? I know the version in the i.superpixels.slic addon and have some
memory of you implementing it elsewhere.
I want to put it in the library, but would like to simplify the cache a bit
before putting it in the library. Be aware that addons need their local
version of this cache, otherwise they won't compile against previous
versions of GRASS 7.
>> On Tue, Dec 12, 2017 at 10:51 AM, Moritz Lennert <
mlennert at club.worldonline.be <mailto:mlennert at club.worldonline.be>> wrote:
>> Hi Anna, Hi Vaclav,
>> I would love to use the i.edge module. However, the fact that it
>> reads everything into memory obviously limits its use either to
>> small images, or to tiled versions of larger images.
>> I have just rapidly looked at the code, but I cannot really detect
>> any place where you really need the entire image, or ? The Gaussian
>> filter could be cut off at a certain distance and the actual Canny
>> detector is also based on a kernel, AFAICT. So, do you think this
>> could be rewritten to use the SEGMENT library and at all times only
>> load necessary parts of the image into memory ?
> grass-dev mailing list
> grass-dev at lists.osgeo.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the grass-dev