Peter Corke

More thoughts. Key ideas to include/take forward: - auto generation of SUM and PROD blocks by + and * operators - replace existing * operator with >>, makes direction of...

Here we go. ``` import numpy as np from matplotlib import cm import pyvista as pv with np.load('data.npz') as data: X = data['X'] Y = data['Y'] Z = data['Z'] image...

And yes, `use_bounds=True` fixes it. Texture mapping not something I'm very familiar with so the documentation is wasted on me, I was just reading the pictures and examples :) Thanks....

And it works with an RGB image as well. I dropped back to greyscale to simplify the debugging.

Thanks for your help. Indeed my data is jumpy, it has some significant outliers. I don't know much about VTK but `vtkRenderWindow` seems to have support for stereo display, anaglyphs...

Why did you remove the` jointdynamics` method? It's quite independent of the payload change that you did? Also, do you have code that you used to test the new functionality...

I'm not sure double() is the right name for this. Generally double() converts some representation to a native vector/matrix representation. Perhaps simplify() or symeval() or something.

They should agree, so long as they are all referenced to the same coordinate frames. Some code gives results referenced to link frames, others to CoG frame. Can you confirm...

Astar was contributed code but no longer maintained by its author, sorry.

The original 1980s paper by Khatib.