Skip to content

Conversation

@jschleicher
Copy link
Contributor

Since this is expected behaviour, if no start time is given in header of the message.

The warning about dropped points isn's useful, if the first point just contains
the expected start point. Dropping it is expected behaviour, thus degrading this
to a debug output message.

A subsequent feature could be to check the current position against the
parametrized tolerance of this point.

Closes #291

…iour

The warning about dropped points isn's useful, if the first point just contains
the expected start point. Dropping it is expected behaviour, thus degrading this
to a debug output message.

A subsequent feature could be to check the current position against the
parametrized tolerance of this point.

Closes ros-controls#291
Copy link
Member

@bmagyar bmagyar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the update!

Copy link
Contributor

@mathias-luedtke mathias-luedtke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Basically, I am okay with this patch (as discussed offline..).
However, I am a little bit worried about the skipping of the first point (which is unrelated to this PR),
Does this really prevent from showing the message in your tests?

return Trajectory();
}
else if ( // If the first point is at time zero and no start time is set in the header, skip it silently
msg.points.begin()->time_from_start == ros::Duration(0.) &&
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not .isZero()?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please chnage this, there is no need to call the constructor and the comparison operator instead of using the function that was implemented for this purpose.

}
else if ( // If the first point is at time zero and no start time is set in the header, skip it silently
msg.points.begin()->time_from_start == ros::Duration(0.) &&
msg.header.stamp == ros::Time(0) &&
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

again, .isZero()?

@davetcoleman
Copy link
Member

I hate that message, glad its going away!

@graiola
Copy link
Member

graiola commented Oct 27, 2018

I am waiting for that pr to merge also #367

@mathias-luedtke
Copy link
Contributor

I went ahead and just updated this PR to use isZero. If the tests pass, I will sqash-merge and update #367

@mathias-luedtke mathias-luedtke merged commit 0cfdcf4 into ros-controls:kinetic-devel Oct 27, 2018
@jschleicher
Copy link
Contributor Author

Thank you @ipa-mdl for pushing it directly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

5 participants