Open gavanderhoorn opened 4 months ago
@ted-miller: would it not make sense to refuse to execute a trajectory which has this problem?
We iterate over all trajectory points when processing the incoming goal, and this seems like it falls in the "malformed input trajectory" category.
In this case, I don't see a problem with that trajectory. It just seems the last point is duplicated.
If there were any positional difference in the last two points, then yeah this would be problem.
So maybe only reject the trajectory if there's no difference, but there is a difference in position?
Just happened to notice it while working on something:
this could be a problem with the 'input' trajectory (ie: the submitted goal), but I haven't checked yet.
Trajectory generated by MoveIt.