<div dir="ltr">grass-devs,<div><br></div><div style>anyone has a timeline for merging the OpenCL code into trunk?</div><div style><br></div><div style>Cheers,</div><div style>Yann</div></div><div class="gmail_extra"><br><br>
<div class="gmail_quote">On 29 January 2013 21:00, Seth Price <span dir="ltr"><<a href="mailto:seth@pricepages.org" target="_blank">seth@pricepages.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto"><div>Also, OpenCL can run as both multicore CPU and GPU. OpenMP can only run on CPU but it's much easier to program. I vaguely recall the OpenCL speed up over single thread on the order of 20x - 50x. If you're looking for a consultant to do additional OpenCL work, I might be able to help.<br>
<div>~Seth</div><div><br></div>via<span> iPhone</span></div><div class="im"><div><br>On Jan 29, 2013, at 8:01 AM, Yann Chemin <<a href="mailto:yann.chemin@gmail.com" target="_blank">yann.chemin@gmail.com</a>> wrote:<br>
<br></div></div><div><div class="h5"><blockquote type="cite"><div><div dir="ltr">Hi,<div><br></div><div>OpenMP first to leverage the actual CPU development routes.</div><div>OpenCL second to leverage the actual GPU routes.</div>
<div><br></div><div>Cheers,</div><div>
Yann</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 29 January 2013 19:11, Newcomb, Doug <span dir="ltr"><<a href="mailto:doug_newcomb@fws.gov" target="_blank">doug_newcomb@fws.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I would vote for multicore OpenMP/OPENCL. I just purchased an 8 core AMD Vishera MB and CPU combo for under $300US to use at home , which is faster than the 8 core Xeon server system I used to do statewide solar irradiation modeling at work for a 755 Million cell grid for 365 days (half hour increments) in 2011. With the advances in multicore architecture ( who knows what core densities ARM will bring?) and utilization of the processing elements in video cards, I think you will benefit many more users on going the multicore route.<div>
<br></div><div>Doug<div><div><br><br><div class="gmail_quote">On Tue, Jan 29, 2013 at 8:05 AM, Ruzicka Jan <span dir="ltr"><<a href="mailto:jan.ruzicka@vsb.cz" target="_blank">jan.ruzicka@vsb.cz</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Dear developers,<br>
<br>
We are planning to rewrite the module r.sun for parallel computation and would like to ask you, which platform is more desired by the GRASS community. To our understanding there are two main ways of development. Either we design it for multi-core desktop systems that use shared memory (for example with use of OpenMP) or create module for large clusters with use of MPI library.<br>
<br>
Which way do you think would benefit GRASS more?<br>
<br>
Best regards<br>
<span><font color="#888888"><br>
Jan Ruzicka<br>
_______________________________________________<br>
grass-dev mailing list<br>
<a href="mailto:grass-dev@lists.osgeo.org" target="_blank">grass-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/grass-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/grass-dev</a><br>
</font></span></blockquote></div><br><br clear="all"><div><br></div></div></div><span><font color="#888888">-- <br><div>Doug Newcomb</div><div>USFWS</div><div>Raleigh, NC</div><div><a href="tel:919-856-4520%20ext.%2014" value="+19198564520" target="_blank">919-856-4520 ext. 14</a> <a href="mailto:doug_newcomb@fws.gov" target="_blank">doug_newcomb@fws.gov</a></div>
<div>---------------------------------------------------------------------------------------------------------</div><div>The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats.</div>
</font></span></div>
<br>_______________________________________________<br>
grass-dev mailing list<br>
<a href="mailto:grass-dev@lists.osgeo.org" target="_blank">grass-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/grass-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/grass-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><div><div>Yann Chemin<br>
</div><div>Researcher@IWMI<br></div>Skype/FB: yann.chemin<br></div><br></div>
</div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>grass-dev mailing list</span><br><span><a href="mailto:grass-dev@lists.osgeo.org" target="_blank">grass-dev@lists.osgeo.org</a></span><br>
<span><a href="http://lists.osgeo.org/mailman/listinfo/grass-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/grass-dev</a></span></div></blockquote></div></div></div></blockquote></div><br><br clear="all"><div>
<br></div>-- <br><div dir="ltr"><div><div>Yann Chemin<br></div><div>Researcher@IWMI<br></div>Skype/FB: yann.chemin<br></div><br></div>
</div>