#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.

I've been working on a #space #visualization tool for our operators. It basically needs to always know, and be ready to plot, where every single one of 60k+ objects is down to millidegree/meter/second resolution just in case the sensor suddenly slews there

My own constraint is that it has to be 1) a single 2) #python executable because otherwise I'm not interested

Earlier this year, I found a great 30x faster technique for determining which #satellites are above the horizon. (In fact, it's far more general than that, but that's all the help it gives me to this problem.)

I also realized I could spawn a #multiprocessing child to do lookahead on data and then pass a huge #numpy array to my graphing process. (Investigated ~9 different ways, chose the best)

But there I was stuck.

At any given moment, there are ~4500 space objects above the horizon (at our latitude). Putting 4500 points with little persistence trails and labels and then updating all that at 1Hz let alone the 10Hz I'd like was taking too long, even using the amazing #pyqtgraph

So there I was stuck. Until this week.

Next minor task since I'm waiting on feedback for #PyQtGraph changes I'm trying to make; try and implement Custom sections in numpydoc (see: https://github.com/numpy/numpydoc/issues/202 ).

I should note, I have no idea how sphinx extensions work, but this feature would be very useful to #PyQtGraph and judging by the number of linked issues, quite a few other libraries.

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

Every time I update the sphinx theme for #PyQtGraph I get a different CSS coloring issue.

For the record, I'm throwing no shade at the theme maintainers, it's not their fault that I'm probably modifying the underlying CSS in a way that is so bizarre that nobody that has any resemblance of knowing what they're doing would do 😂