Peter David Fagan

> That would be most welcome. There are a few changes Jean has reported elsewhere that it sounds like we should merge and which you might benefit from, too. Thanks...

@ozangungortuhh did you perform this calibration on an earlier version of ROS while waiting for this to get ported? I think that is currently the strategy to take. I am...

Hi @Sumanth-Pashuparthi, I don't think this has been ported yet. I created an unofficial lightweight package for my own work [here](https://github.com/peterdavidfagan/moveit2_camera_calibration/tree/main). It's integrated into my own workspace stack so likely...

Hi @henningkayser, I'll look to set aside time this weekend to review this as its been a while since I built the docs locally.

+1 also interested in this feature for data collection purposes. Would be nice to incorporate planning sequences in `moveit_cpp`.

Thanks for flagging this @yulat214 I hope to look into this soon.

> When executing motion_planning_python_api_tutorial.launch.py from moveit2_tutorial, Rviz shows NO PLANNING LIBRARY. This is expected, the Python API is supposed to be used directly within your script in order to define...

Closing for now as I went with the approach outlined in existing issues. Initial code is [here](https://github.com/peterdavidfagan/mujoco_ros) but its kind of messy.

This is super useful, thanks @BarisYazici.

> If you get something ready, we could make it available to public. So more developers can utilise it. Right now my code is more of a proof of concept...