<div dir="ltr"><div>Thanks all for the inputs.</div><div>In the end I implemented a scripting procedure outside grass using pktools (pkfilter). </div><div>I first tiled the image with some overlap area, than run pkfilter -f stdev , than crop the overlap area and then merge back the full image. </div><div><br></div><div>Best Regards </div><div>Giuseppe <br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 28 May 2017 at 17:21, Markus Metz <span dir="ltr"><<a href="mailto:markus.metz.giswork@gmail.com" target="_blank">markus.metz.giswork@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span class=""><div><br><br>On Fri, May 26, 2017 at 5:04 PM, Giuseppe Amatulli <<a href="mailto:giuseppe.amatulli@gmail.com" target="_blank">giuseppe.amatulli@gmail.com</a>> wrote:<br>><br>><br>> Hi all,<br>> I'm running r.neighbors for a global 250m raster with window-size setting larger than 100 pixels.<br>> The computation take almost 1 week and i'm thinking if there is a way to speed up the process. <br>><br>> I know how to set-up a multi-region & multi-core computation and working in tiles but I would avoid due to the difference that I would encounter in the tile borders (and tile overlap will be required).<br><br></div></span>Tiling would speed up the process. What is the problem with overlapping tiles? You can set up overlapping tiles, cut the results such that they are not overlapping each other and patch them in the end.<br><div><br></div><div>Markus M<br></div><div><span class=""><br>><br>> Is it possible to run r.neighbors in parallel or increase the memory that r.neighbors would use (as developed in r.watershed)?<br>><br>> Thank you<br>> Best <br>> Giuseppe <br>><br>><br>><br>><br>> --<br>> Giuseppe Amatulli, Ph.D.<br>><br>> Research scientist at<br>> Yale School of Forestry & Environmental Studies<br>> Yale Center for Research Computing<br>> Center for Science and Social Science Information<br>> New Haven, 06511<br>> Teaching: <a href="http://spatial-ecology.org" target="_blank">http://spatial-ecology.org</a><br>> Work: <a href="https://environment.yale.edu/profile/giuseppe-amatulli/" target="_blank">https://environment.yale.edu/<wbr>profile/giuseppe-amatulli/</a><br>><br></span><span class="">> ______________________________<wbr>_________________<br>> grass-user mailing list<br>> <a href="mailto:grass-user@lists.osgeo.org" target="_blank">grass-user@lists.osgeo.org</a><br>> <a href="https://lists.osgeo.org/mailman/listinfo/grass-user" target="_blank">https://lists.osgeo.org/<wbr>mailman/listinfo/grass-user</a><br><br></span></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>Giuseppe Amatulli, Ph.D.<br><br>Research scientist at<br><span>Yale School of Forestry & Environmental Studies<br></span><span>Yale Center for Research Computing<br></span>Center for Science and Social Science Information<br>New Haven, 06511<br><div>
Teaching: <a href="http://spatial-ecology.org" target="_blank">http://spatial-ecology.org</a>
</div>
Work: <a href="https://environment.yale.edu/profile/giuseppe-amatulli/" target="_blank">https://environment.yale.edu/profile/giuseppe-amatulli/</a> <br></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
</div>