PyQtGraph VS nasa-ingenuity-helicopter

PyQtGraph - Interactive and realtime 2D/3D/Image plotting and science/engineering widgets.

Image, 3D, or data visualization applications using OpenCV and the SciPy ecosystem. The Graphics View Framework can display an image and let the user interact with it, and the Python ecosystem is very rich for image processing, data analysis, and visualization. For example, LabelMe for image labeling, PyQtGraph for scientific graphics, or custom QWidget integration in Maya.

I don't think that's related to your error though - from the backtrace, it looks like the plotWidget has plotItem attribute that's somehow been assiged to itself (or maybe some other PlotWidget) , so is just endlessly recursing as it tries to proxy the same attribute lookup (presumably 'clear') to itself. Looking at the source, the plotitem is either created as a new PlotItem() object if not provided, or passed in to the constructor, so I'd check how this gets initialised - eg. does this get set as a property in your .ui file? Are you setting it to the widget itself somehow?

I did something like this recently but I used pyqtgraph: https://www.pyqtgraph.org/

Ah, I agree, Matplotlib is for publication, so slow and pretty. For fast, I use pyqtgraph, which can do that 10 million point plot interaction. And since it's QT, it integrates seamlessly into QT applications.

I found out last weekend that one of the Open Source code projects I contribute to is being used to help fly the Ingenuity helicopter on Mars. I think it's really awesome that I, along with a ton of other people, contributed in some small way to a freaking helicopter flying on Mars. Diabetes be damned!

> The University's financial position remains strong with assets of $6.3 billion, an increase of $0.2 billion from fiscal year 2017

In the end to me it seems the value realized in this could not be a demonstrateably improved kernel patch review process without another non-consensual round of buggy patch submissions so it is very important to consider precedent and posture now. Arguably the immediate value realized has been the identification of a number of (historically) maybe not so great collaborators.

> Another lesson is something we already knew: kernel maintainers (and maintainers of many other free-software projects) are overworked and do not have the time to properly review every patch that passes through their hands. They are, as a result, forced to rely on the trustworthiness of the developers who submit patches to them.

Spot on.

> The kernel development process is, arguably, barely sustainable when that trust is well placed; it will not hold together if incoming patches cannot, in general, be trusted.

Hold off on that pessimism, we got a great thing going here and on the way to Mars, pat on the back:

> https://github.com/readme/nasa-ingenuity-helicopter

I did read the apology, it is a good apology, as a member of "Linux communities" (linux from 15yo) apology accepted. My intent is not to harm any reputations but clearly communicate my belief in the need to consider how this research may be used as precedent.

GitHub posted a really cool article about how open source powered Ingenuity: https://github.com/readme/nasa-ingenuity-helicopter. In there is a link to a list of all the projects used as well!

Open Source on Mars: Community powers NASA’s Ingenuity Helicopter. Nearly 12,000 people contributed code, documentation, graphic design, and more to the open source software that made Ingenuity’s launch possible. To celebrate this moment in open source history, GitHub added a new badge to profiles of those contributors. [GITHUB]

This post goes into a little more detail on what was used and its purpose: https://github.com/readme/nasa-ingenuity-helicopter