#pyqtgraph — Public Fediverse posts

I'm on this project where we want to do #realtime #radar but are sort of starting with nothing (apart from world-class radar transmitters, receivers and expertise...)

One very smart but non-#software person wrote a bunch of good #signalprocessing #code and some "gets the job done" #gui code

Or it did until we went higher bandwidth

Last week I rewrote all the non-sigproc parts into #pyqt and #pyqtgraph. Today I benchmarked both.

Exactly the same speed....except pyqtgraph is

THREE ORDERS OF MAGNITUDE

faster than #matplotlib

#python peeps, please hear me. mpl has its place and uses. High data rate animated displays is not that place.

It's one of THOSE days

I overslept by an hour. The tuxedo #cat had to use his little paws to roll me out of bed. (He was hungry but worse I was not On Schedule, something he cares about a LOT)

But also I only had to get up early because #IT made some change on my laptop that prevents me from logging in to #wfh

When I got here, I found that a request I put in to unlock an unrelated account on a different network had ALSO not been done. But at least the ticket is closed!

And the thing I have to work on is annoying. A project I definitely want to be on needed a display. I made one in #python #pyqt #pyqtgraph.

Oh, they meant a #web #app. OK, so I redesigned the backend to both would work.

Everyone likes THAT except for some external guy who AFAICT hasn't done any actual work on this project. The only reason his opinion matters is that he's the one actually deploying the app...?

And instead of modifying the code to be how he wants it he wrote a sample app for ME to follow?

And I don't think that's even going to work. #plotly needs a session ID to get persistent zoom and some other things right. This guy's design means everyone has to share a session ID. I explained this to him.

So the outcome of starting from his code is either that I'll be proved wrong or I'll have wasted a day proving HIM wrong. Two wonderful possibilities.

I love #pyqtgraph for 2D scientific and #dataviz #graphs in #python. And now I'm starting to really love #vtk for 3D.

https://vtk.org/

It has a lot of the same #science adjacent type plotting. It works well with python. (And there's a #javascript #api but I haven't used it...yet). And it is *extremely fast*.

The only problem is that there's a lot to it and I don't really understand the workflow. (I feel like there's an extra layer. There's a "source", a "mapper", an "actor" and a "renderer". One of those seems superfluous.)

There are a lot of examples on their site and elsewhere. And there's a lot of documentation. But I haven't yet found a good combination tutorial that has worked examples that are also explained.

I really just have to use it more and get it into my head.

Fortunately, I have a weird #math/#geometry/#orbitalmechanics thing I want to try to solve (or at least visualize). Intersections of multiple ellipsoids and cones....

#dataviz is critical, but I don't think in pictures, I think in spatial relations and movement (is this an #adhd thing?)

Movement happens in time and you usually want to viz the time axis all at once, so I've trained myself to turn "$variable vs t" into mental motion

Other times you need an interactive #ux and that usually means 3D

I love love love #pyqtgraph for #python plotting but they will be the first to tell you the 3D needs some love

My punfully-named work project has proved to be a hit[1] and I managed to get an 30y-experienced #software #developer *with an #astronomy degree* assigned to it. (This is a #space application)

She agreed that the 3D portion was neat but hard to use. She found #vtk, which seems to be the perfect partner because it does 3D really well, stays out of 2D and has a #pyqt connector.

I just worked through a tutorial and, yeah, this could be a huge breakthrough in my viz apps.

[1]They think they want to change the pun name but they are wrong. An unforgettable name is money in the bank.

Do you use #PyQtGraph with conda versions of #PySide bindings? Then this issue is very relevant to you. Please upvote:

https://bugreports.qt.io/plugins/servlet/mobile#issue/PYSIDE-3031

Prompt: Black on black.

(I deliberately skipped Prompt 3, "Exactly 42 lines of code." which seemed both too constricting and not constricting enough.)

#genuary #genuary2025 #genuary4 #python #pyqtgraph

#genuary

Layers upon layers upon layers.

I still like the basic idea here, but I couldn't make it work on multiple levels (how ironic).

I spent several hours trying to understand how color compositing works in general and in #qt in particular. I kind of got something fragile sort-of working.

When I gave up on Making It Perfect, I realized that looping a blizzard is unlikely to work.

Welp. This is a #learning #python #pyqtgraph project anyway and that goal was accomplished.

#genuary2025 #genuary2

It's February 1 and you know what that means!

#GENUARY!!

This is my first ever entry. Prompt is "Vertical or horizontal lines only."

#genuary2025 #genuary1 #python #pyqtgraph

Lastly, for #PyQtGraph developers, we now have stub files for getting auto-completion when using pyqtgraph.Qt, which is PyQtGraph's Qt abstraction layer. This layer is not intended to be used outside of #PyQtGraph, if you want a Qt abstraction layer for your project, we recommend the #QtPy library.

We have had a stub file there for a while, but it only worked in PyCharm, the stubs now work with pyright and PyCharm now.

#PyQtGraph 0.13.5 is out! While not our largest release, it has something for everyone! Note, this release is the last to support #Python
3.9 and #NumPy 1.22.

First, ImageItem got another substantial performance boost, especially if you're using #numba but there is a significant boost for #NumPy users as well.

A ColorMapMenu was added to ColorBarItem, allowing for users to be able to change color maps interactively instead of programmatically.

#DataViz #PyQt #Qt

@fluiddyn The #PIV image case would be a good one for #PyQtGraph, given our origins of working with 2D slices of “3D images". Please don't hesitate to reach out if you could use assistance with plotting or trying to improve performance.

@pyqtgraph
Another place where we have actually used #PyQtGraph is in #fluidimage to compare #PIV images and velocity fields.

https://foss.heptapod.net/fluiddyn/fluidimage/-/tree/branch/default/fluidimage/gui