Michael Görner

I did not read this thread before because the name did not at all represent the discussed problem, but @felixvd pointed me here in [another related issue](https://github.com/ros-planning/moveit_tutorials/issues/465#issuecomment-810685490). Missing support for...

> Does this give you an advantage over sending the trajectory directly to the robot driver? > It would still leave you without collision checking between the trajectories from what...

Personally, I would prefer to deprecate warehouse-ros-mongo altogether in favor of https://github.com/gleichdick/warehouse_ros_sqlite . However, if anyone provides a patch for the Mongo API migration, we will be happy to accept...

> @v4hn I like this idea as well; What would the process be to "adopt" the warehouse_ros_sqlite into ros-planning? It's basically on the way and was discussed in the maintainer...

> Are there any plans to support the robotiq grippers on ROS2? We don't have any concrete plans right now to migrate our own hardware platform to ROS2. But even...

I just noticed the same mistake exists in https://github.com/facontidavide/rosx_introspection , not sure about others.

Imo, the key issue that provoked your question is that the PILZ planner [abuses `max_*_scaling_factor`](https://github.com/ros-planning/moveit/blob/9440572fe08618f643d3c93105f193ee58cbb7d5/moveit_planners/pilz_industrial_motion_planner/src/trajectory_generator.cpp#L274-L275) (1.) to apply in Cartesian space whereas [they are documented to apply only to the...

Lesson taught: never give tangible time frames in pre-announcements on the internet :-) > The code associated with Simple will be released as open-source in the next few weeks

Hi Justin, nothing bad really. It's just that most people do not expect 4+ months when an announcement states `the next few weeks`. I gave similar timelines in the past...

Thank you for the analysis. Could you provide a pull-request and ideally a test that works?