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
Describe the bug
When the shouldFlipPath boolean supplier returns true, the target pose interpolation does not work. The behavior is that PathPlanner appears to be interpolating in the direction of the original unflipped path.
Set the alliance to Blue (while "Disconnected") and run autonomous. Use the AdvantageScope Odometry tab to view the "Target Pose" field (use the Connect to Simulator feature).
Set the alliance to Red (while "Disconnected") and re-run autonomous. Use the AdvantageScope Odometry tab to view the "Target Pose", and note the incorrect behavior.
Expected behavior
The behavior on the Red alliance should match the Blue alliance, just flipped.
Screenshots
Below is a zip with a video of the correct (blue) and incorrect (red) behavior. PathPlanner-beta-6-bug.zip
Versions: (please complete the following information):
OS: Windows 11
GUI Version: n/a
PPLib Version: 2025.0.0-beta-6
PPLib Language: Java, C++, Python
Additional context
This issue was likely introduced with the changes in #935.
The text was updated successfully, but these errors were encountered:
bhall-ctre
changed the title
Target Pose interpolation does not work with alliance flipping
Beta-6 Target Pose interpolation does not work with alliance flipping
Dec 20, 2024
Describe the bug
When the
shouldFlipPath
boolean supplier returnstrue
, the target pose interpolation does not work. The behavior is that PathPlanner appears to be interpolating in the direction of the original unflipped path.To Reproduce
Steps to reproduce the behavior:
configureAutoBuilder()
, add a logger for the target pose callback:Expected behavior
The behavior on the Red alliance should match the Blue alliance, just flipped.
Screenshots
Below is a zip with a video of the correct (blue) and incorrect (red) behavior.
PathPlanner-beta-6-bug.zip
Versions: (please complete the following information):
Additional context
This issue was likely introduced with the changes in #935.
The text was updated successfully, but these errors were encountered: