Martin Pecka

Try the new version, I had to force `_pywrap_tensorflow_internal` to be linked to the binaries, because it is left out by the linker since TF 1.5+ (or so). That's because...

And, moreover, if you're buulding TF yourself, you might consider not using the pip TF. New version of tensorflow_ros allows you to link against a custom build of TF.

What about running https://github.com/tradr-project/static_transform_mux during the recording? That would "ensure" that the last published `/tf_static` message would contain all the transforms needed for replay. Moreover, you could even add more...

Fix provided in https://github.com/ros/common_msgs/pull/184 . Feel free to leave some comments there. And thanks for the research you did!

Do you think a build time deprecation/warning or rather a runtime warning would be suitable? It might be nice to actually check if the given transform is an isometry or...

Deprecation warnings added in #371 .

Noetic continuation in #561.

Relevant links I used when setting up the WSL 2 GPU support: Install newest GPU drivers: https://learn.microsoft.com/en-us/windows/wsl/tutorials/gui-apps Resolve a problem with clock inside the WSL 2 container: https://stackoverflow.com/questions/65086856/wsl2-clock-is-out-of-sync-with-windows Install singularity...

Thanks. For us, the workaround described here is enough. So I meant this issue only as a kind of kickstarter for somebody else who would like to work on it.

Okay, feel free to do it as you like/need. I think it'd be relatively easy to repeat the changes in a new PR.