<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.DefaultFontHxMailStyle
{mso-style-name:"Default Font HxMail Style";
font-family:"Calibri",sans-serif;
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link=blue vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal><span class=DefaultFontHxMailStyle>Markus, Helmut,<o:p></o:p></span></p><p class=MsoNormal><span class=DefaultFontHxMailStyle><o:p> </o:p></span></p><p class=MsoNormal><span class=DefaultFontHxMailStyle>Thank you both for the extra information! I’ll attempt to work a solution using your method and see if it helps speed up that part of our workflow.<o:p></o:p></span></p><p class=MsoNormal><span class=DefaultFontHxMailStyle><o:p> </o:p></span></p><p class=MsoNormal><span class=DefaultFontHxMailStyle>Thanks!<o:p></o:p></span></p><p class=MsoNormal><span class=DefaultFontHxMailStyle>Brett</span></p><p class=MsoNormal><span class=DefaultFontHxMailStyle><o:p> </o:p></span></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:neteler@osgeo.org">Markus Neteler</a><br><b>Sent: </b>Saturday, December 18, 2021 9:17 AM<br><b>To: </b><a href="mailto:Synper311@aol.com">Synper311</a><br><b>Cc: </b><a href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a><br><b>Subject: </b>Re: [GRASS-user] Inquiry about GRASS GIS Windows Binary Stand-Alone Build Configuration</p></div><p class=MsoNormal><span class=DefaultFontHxMailStyle><o:p> </o:p></span></p><p class=MsoNormal>Hi,</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>On Fri, Dec 17, 2021 at 9:27 PM Synper311 via grass-user</p><p class=MsoNormal><grass-user@lists.osgeo.org> wrote:</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> Hi,</p><p class=MsoNormal>><o:p> </o:p></p><p class=MsoNormal>> Just writing to inquire if the GRASS GIS Windows Binary Stand-Alone Builds are using the –with-openmp Build Configuration flag to enable multithreading across all applicable modules.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>(see the email by Helmut)</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>> Tangential to this question is whether or not it is expected that r.contour will use N-Number of threads when processing</p><p class=MsoNormal>> on a system with greater than 4 threads. This question arises as it was observed to only use 4 threads on a Ryzen</p><p class=MsoNormal>> machine with 24+ threads.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>To my knowledge these commands have openMP support so far:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>r.proj</p><p class=MsoNormal>r.series.accumulate</p><p class=MsoNormal>r.sim.sediment</p><p class=MsoNormal>r.sim.water</p><p class=MsoNormal>r.sun</p><p class=MsoNormal>v.surf.rst</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>and several more are in the pipeline:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>https://github.com/OSGeo/grass/pulls?q=is%3Apr+is%3Aopen+openMP</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>> For a bit more context, this all relates to the usage of the Binary GRASS GIS files being used within the context of generating contours within WebODM (OpenDroneMap).</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Would be nice to see r.contour to be the next candidate!</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Alternative solution (say, an idea) for now:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>- r.tile the data into chunks (perhaps with small overlap, not sure if</p><p class=MsoNormal>needed or useful)</p><p class=MsoNormal>- run r.contour on the tiles, in parallel (SLURM, gnu-parallel, something else)</p><p class=MsoNormal>- v.patch the resulting vector maps</p><p class=MsoNormal>- v.build.polylines to generate polylines from lines</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Best,</p><p class=MsoNormal>Markus</p><p class=MsoNormal><span class=DefaultFontHxMailStyle><o:p> </o:p></span></p></div></body></html>