Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TrajectoryAborted exception #195

Closed
jeking04 opened this issue Sep 30, 2015 · 2 comments
Closed

TrajectoryAborted exception #195

jeking04 opened this issue Sep 30, 2015 · 2 comments

Comments

@jeking04
Copy link
Contributor

Current, the TrajectoryAborted exception is raised if ExecuteTrajectory is called with the robot in a configuration that does not match the first waypoint in the trajectory:

https://github.com/personalrobotics/prpy/blob/master/src/prpy/base/robot.py#L453

Previously, the TrajectoryAborted exception was used to indicate that owd aborted the trajectory.

This issue is two parts:

  1. I can't tell if the TrajectoryAborted exception is still raised when owd aborts a trajectory. Can we verify this is still the case?
  2. If it is, can we change the exception thrown when the first waypoint doesn't match the configuration?

This will allow us to differentiate between trajectories not successfully executed by owd and trajectories that never get sent to owd bc they are flawed.

@psigen
Copy link
Member

psigen commented Sep 30, 2015

Does #196 make sense?

@mkoval
Copy link
Member

mkoval commented Oct 9, 2015

Fixed in #196.

@mkoval mkoval closed this as completed Oct 9, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants