Gonzalo Casas

@jf--- sure! it would be great!

Done in #356

That RAPID parser is a very interesting project. This feature is still up for definition and your feedback is more than welcome! The overall idea goes slightly more in the...

Hi @pblcc ! Great! Yes, we have a place that would make sense, I would suggest to put these examples under the `examples/02_description_models` together with other related examples: https://github.com/compas-dev/compas_fab/tree/main/docs/examples/02_description_models Thanks!

yep, we're splitting up all these features (FK, IK, planning, etc) into pluggable `BackendFeature` implementations (see https://github.com/compas-dev/compas_fab/issues/99 for a placeholder issue of that work) with the idea of having generic...

@garyedwards thanks! Cartesian planning is still an open point in our roadmap before `1.0` release; for now, we're mostly ignoring the timing information of MoveIt planner and use a different...

Awesome! The first step towards this would be to prepare a Docker image building master with Pilz (since I believe it's not yet released). Once that is done, probably the...

If it's exposed over a different ROS service, I would probably lean towards a new `move_it_plan_sequence_motion.py` instead of extending the current plan motion one. @beverlylytle what do you think? >...

Which version of `compas_fab` are you using? There are several unrelated issues here, but I think one big difference is that when you load from urdf (not from ROS), you...

Prototype available in https://github.com/dbt-ethz/A032-CE3DP/blob/master/CE3DP%20slicer/cSlicer/partial_order_plan.py