<div dir="ltr"><div><div>I'll take a look, thank you.<br><br></div>So you are suggesting me to start form the VisPy code? Is there someone who I can refer in case I will need some clarification?<br><br></div>Francesco Faccenda<br></div><div class="gmail_extra"><br><div class="gmail_quote">2017-09-14 15:50 GMT+02:00 Benjamin Root <span dir="ltr"><<a href="mailto:ben.v.root@gmail.com" target="_blank">ben.v.root@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>That was one of the old attempts (but not the oldest). It doesn't seem like it ever intersected with the vispy project, though, so it is likely all that exists.<br><br></div>I would also look at <a href="https://www.youtube.com/watch?v=_3YoaeoiIFI" target="_blank">https://www.youtube.com/watch?<wbr>v=_3YoaeoiIFI</a><br></div>Luke does a nice job providing an overview of the vispy package. One of the most exciting things that the matplotlib and vispy devs were discussing at scipy 2015 was the possibility of making a matplotlib backend out of some parts from vispy. It was attractive because the vispy folks were actively working on improving their opengl code and packaging to make it work on a wide variety of hardware and setups. They had supposedly even implemented a headless opengl mode, too, which was very important for us.<br><br></div>Cheers!<br></div>Ben Root<br><br></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 14, 2017 at 9:34 AM, Francesco Faccenda <span dir="ltr"><<a href="mailto:f.faccenda86@gmail.com" target="_blank">f.faccenda86@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"><div><div><div><div>Thank you, Ben.<br><br></div>unfortunately I don't have experience developing opengl neither, but I'd like to make an attempt riesuming this subject.<br><br></div>I am starting from this: <a href="https://github.com/ChrisBeaumont/mplgl" target="_blank">https://github.com/ChrisBeaumo<wbr>nt/mplgl</a><br><br></div>Can anyone confirm this is the last update we have for this project?<span class="m_5483910239296006561HOEnZb"><font color="#888888"><br><br></font></span></div><span class="m_5483910239296006561HOEnZb"><font color="#888888">Francesco Faccenda</font></span></div><div class="m_5483910239296006561HOEnZb"><div class="m_5483910239296006561h5"><div class="gmail_extra"><br><div class="gmail_quote">2017-09-13 16:21 GMT+02:00 Benjamin Root <span dir="ltr"><<a href="mailto:ben.v.root@gmail.com" target="_blank">ben.v.root@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>A bit of background regarding efforts in this area...<br><br></div>A long time ago, some experiments were done to see if an opengl backend could be made for matplotlib. The results weren't that great, particularly for text rendering, so the effort was dropped. The core developers all agree that an opengl backend would be neat to have, but we all have limited, if any, experience developing opengl. Furthermore, such a backend would likely require a lot of rapid development and trial-n-error. So, we encouraged others to go develop a package or two separately, with the eye for bringing it back into matplotlib when it was ready. Glumpy and a few other projects were born from that prodding.<br><br></div>VisPy was an attempt to consolidate the development efforts for those projects. The matplotlib devs had very fruitful discussions with some VisPy devs back at SciPy 2015, but the project became non-responsive shortly afterwards.<br><br></div>Ben Root<br><br></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="m_5483910239296006561m_8144903429515423810h5">On Wed, Sep 13, 2017 at 3:31 AM, Francesco Faccenda <span dir="ltr"><<a href="mailto:f.faccenda86@gmail.com" target="_blank">f.faccenda86@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="m_5483910239296006561m_8144903429515423810h5"><div dir="ltr"><div><div><div>Thank you Chris for your reply.<br><br>I have to admit I already stumbled on VisPy while doing my research on the web. Still, I've got a lot of code already working with <i>matplotlib</i>. Indeed, not only I plot data with it, but i manage a lot of <i>mpl events</i> to provide the users usefool tools, like lines picking, tooltips, lines copy/paste, square selectors for multiple selections, context menu and so on. Moreover, I got matplotlib <b>embedded </b>on <i>wxpython </i>as well. While at the beginning few lines were managed and noone complained, now that big amout of data has to be displayed, the non-GPU core of the library is starting to show its limits.<br><br></div>Since matplotlib is a reference library for this kind of applications, I thought it deserved an update in this direction. If anyone is willing to do so, I'm available to discuss possible solutions and also provide any help I can give.<br><br></div>Best regards,<br></div>Francesco Faccenda<br><div><div><div class="gmail_extra"><br><div class="gmail_quote">2017-09-13 0:46 GMT+02:00 Chris Barker <span dir="ltr"><<a href="mailto:chris.barker@noaa.gov" target="_blank">chris.barker@noaa.gov</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span>On Tue, Sep 12, 2017 at 8:47 AM, Francesco Faccenda <span dir="ltr"><<a href="mailto:f.faccenda86@gmail.com" target="_blank">f.faccenda86@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><p class="MsoNormal">But there’s a good news, I have a nice GPU available (an NVIDIA Tesla
K40c), so I’d like to know if there is a way to make matplotlib run on it, or
maybe wrap it on some GPU/CUDA wrapper and make it run smoothly.<br></p></div></blockquote><div><br></div></span><div>I tihnk you want VisPy:</div><div><br></div><div><a href="https://vispy.readthedocs.io/en/latest/" target="_blank">https://vispy.readthedocs.io/e<wbr>n/latest/</a><br></div><div><br></div><div>It's a plotting package with a kinda like matplotlib API, built on OpenGL.</div><div><br></div><div>Unfortunately, it doesn't look like it's been updated in a while -- from teh docs. But the gitHub project is active:</div><div><br></div><div><a href="https://github.com/vispy/vispy" target="_blank">https://github.com/vispy/vispy</a><br></div><div><br></div><div>So maybe it's only the docs that haven't been updated!</div><div><br></div><div>But probably a much better option than trying to shoehorn GPU rendering into MPL.</div><div><br></div><div>The problem is that while MPL was designed to be "backend" independent -- so it is "easy" to plug in an alternative renderer, the rendering model is not really well suited to GPU rendering -- it would take a lot of refactoring to really be able to take advantage of the graphics card.</div><div><br></div><div>-CHB</div><span class="m_5483910239296006561m_8144903429515423810m_2770110561794273789m_-9182341938570194908HOEnZb"><font color="#888888"><div><br></div></font></span></div><span class="m_5483910239296006561m_8144903429515423810m_2770110561794273789HOEnZb"><font color="#888888"><span class="m_5483910239296006561m_8144903429515423810m_2770110561794273789m_-9182341938570194908HOEnZb"><font color="#888888"><div><br></div>-- <br><div class="m_5483910239296006561m_8144903429515423810m_2770110561794273789m_-9182341938570194908m_-9015833126011210045gmail_signature"><br>Christopher Barker, Ph.D.<br>Oceanographer<br><br>Emergency Response Division<br>NOAA/NOS/OR&R <a href="tel:(206)%20526-6959" value="+12065266959" target="_blank">(206) 526-6959</a> voice<br><a href="https://maps.google.com/?q=7600+Sand+Point+Way+NE&entry=gmail&source=g" target="_blank">7600 Sand Point Way NE</a> <a href="tel:(206)%20526-6329" value="+12065266329" target="_blank">(206) 526-6329</a> fax<br>Seattle, WA 98115 <a href="tel:(206)%20526-6317" value="+12065266317" target="_blank">(206) 526-6317</a> main reception<br><br><a href="mailto:Chris.Barker@noaa.gov" target="_blank">Chris.Barker@noaa.gov</a></div>
</font></span></font></span></div></div>
</blockquote></div><br></div></div></div></div>
<br></div></div>______________________________<wbr>_________________<br>
Matplotlib-devel mailing list<br>
<a href="mailto:Matplotlib-devel@python.org" target="_blank">Matplotlib-devel@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/matplotlib-devel" rel="noreferrer" target="_blank">https://mail.python.org/mailma<wbr>n/listinfo/matplotlib-devel</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>