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
I have two TrajectoryActionBuilders. After the first one the robot stops and then it executes the second one, but doesn't start from the end of the first one, but instead the path starts at the start of the first one. I am using .fresh() to get a new TrajectoryActionBuilder that should start from the end of the last TrajectoryActionBuilder, but it starts at the start of the first TrajectoryActionBuilder. Manually calculating the end pose of the first path and putting it in as the start pose for the second path works, but it seems like .fresh() should work. Video one shows what happens and video two shows what the path should be, but the robot doesn't stop between the two paths.
It turns out running endTrajectory() before fresh() fixes the problem. To apply this fix replace TrajectoryActionBuilder toBasketBuilder2 = toBasketBuilder1.fresh() with TrajectoryActionBuilder toBasketBuilder2 = toBasketBuilder1.endTrajectory().fresh(). Is this the intended behavior?
I have two
TrajectoryActionBuilder
s. After the first one the robot stops and then it executes the second one, but doesn't start from the end of the first one, but instead the path starts at the start of the first one. I am using.fresh()
to get a new TrajectoryActionBuilder that should start from the end of the last TrajectoryActionBuilder, but it starts at the start of the first TrajectoryActionBuilder. Manually calculating the end pose of the first path and putting it in as the start pose for the second path works, but it seems like.fresh()
should work. Video one shows what happens and video two shows what the path should be, but the robot doesn't stop between the two paths.Code:
The text was updated successfully, but these errors were encountered: