G.A. vd. Hoorn

So I had some time to play with this and first and foremost: nice job @JeroenDM. As to parameter naming, loading and storage: I've gone ahead and tried the minimal...

@Levi-Armstrong: FYI.

I would say that personally I'd like to store any parameters related to the various robots in their respective support packages. I'd like to avoid having joint limits in the...

It's unfortunate there is no "include system" in yaml, as that would immediately solve this: the MoveIt `kinematics.yaml` could just include the OPW parameters yaml and nothing would have to...

> As we have our own more end-user oriented assistant I don't mind changing the generated files now. No, maybe you don't, but I'd have to update 18 moveit configuration...

I have a local branch which explores some options. Adding a `variant` parameter to the launchfiles allowed me to remove all files but those for the base model. Selecting a...

Starting with Jade this may actually be easier / possible, by exploiting the extended expression support (if/else), in-order evaluation, yaml parameter loading and other more advanced features in `xacro`.

You link the Indigo tutorials. Is that because you generated this on Trusty/Indigo? IKFast plugin infrastructure has changed significantly recent years, so I'd like to make sure. Build is currently...

> yesterday I tried and successfully compiled it on Ubuntu 18.04 with ROS Melodic. Yes, CI also succeeds for Melodic. But it fails for Kinetic. As we're supporting both Kinetic...

Apologies for my late reply. I believe controlling external axes is definitely interesting. Here at TUD we have an KR 210 on a 4m rail with 3 additional external axes....