Use first trajectory point as start state for visualization

[henningkayser]

When visualizing trajectories of subgroups the previous implementation would use the shared initial robot state for populating the joint values outside the group. This can have strange effects like apparent link collisions even though the original trajectory is collision free. If we have a robot trajectory with fully populated robot states we should use these instead.

[bmagyar]

This already looks good to me, perhaps you could still emit a warning or an info message that the start state should be defined.

[bmagyar]

I've restarted the CI jobs, 3/3 "succeeded", 2/3 failed on a post-build timeout :-/

[davetcoleman]

Travis error:

moveit_ros/perception/mesh_filter/test/mesh_filter_test.cpp

[davetcoleman]

Have you looked into the failing GPU test?

[davetcoleman]

@henningkayser can you compare .travis.yml from /moveit repo to this repo? maybe there are some changes we need to bring in to fix travis?

[rhaschke]

@henningkayser can you compare .travis.yml from /moveit repo to this repo?

@davetcoleman, there is an open PR (#47) to address the Travis issues waiting for your approval since a month or so.

[davetcoleman]

I had forgot about that PR, thanks Robert!

[rhaschke]

Closing & re-opening to trigger Travis rebuild.