You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Previously, the TrajectoryAborted exception was used to indicate that owd aborted the trajectory.
This issue is two parts:
I can't tell if the TrajectoryAborted exception is still raised when owd aborts a trajectory. Can we verify this is still the case?
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.
The text was updated successfully, but these errors were encountered:
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:
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.
The text was updated successfully, but these errors were encountered: