Skip to content

fix(minimum_rule_based_planner): always shift trajectory start to ego - #3244

Open
mraditya01 wants to merge 4 commits into
feat/v0.64/e2efrom
feat/trajectory-start-to-ego
Open

fix(minimum_rule_based_planner): always shift trajectory start to ego #3244
mraditya01 wants to merge 4 commits into
feat/v0.64/e2efrom
feat/trajectory-start-to-ego

Conversation

@mraditya01

@mraditya01 mraditya01 commented Jul 24, 2026

Copy link
Copy Markdown

Description

Update autoware_minimum_rule_based_planner to always shift the generated trajectory so that it starts from the ego pose.

Previously, trajectory shifting was skipped when both the lateral offset and yaw deviation were below their configured thresholds. This could leave the trajectory start slightly misaligned with the ego pose.

Key changes

  1. Remove the trajectory-shift bypass

    • Removed the early return based on minimum_shift_length and minimum_shift_yaw.
    • The trajectory is now shifted even when the lateral offset and yaw deviation are small.
  2. Update the unit test

    • Replaced the previous no-shift expectation with a check that the shifted trajectory starts at the ego position and orientation.
    • Covers an offset below the former minimum-shift threshold.

Related links

None.

How was this PR tested?

Unit test.

Before

before

After

after

Notes for reviewers

None.

Interface changes

None.

@github-actions

Copy link
Copy Markdown

@mraditya01 Thank you for contributing to TIER IV E2E branch! Edit the checklist below and check the boxes as you complete the items.

Things to check before merging

Please check the following points before merging:

  • Write a brief description of this PR that can be understood by coding-agents.
  • Contact the branch manager on when the PR will be tested on vehicle.
  • Recommend to use Squash and Merge to merge the PR.
  • Report in #team-product-dev channel on the contents of the PR. @ branch manager.

After merging

Please check the following points after merging:

  • Wait for the automatic hash synchronization, which will automatically create a PR to update the hash, you should check the PR and merge it.

@tier4-autoware-public-bot tier4-autoware-public-bot Bot added beta/v0.64 Base branch: beta/v0.64 diffusion_planner Product: diffusion_planner labels Jul 24, 2026
@Kotakku Kotakku added the run:build-and-test-differential After beta/v0.41 label Jul 24, 2026

TrajectoryShiftParams shift_params;
shift_params.minimum_shift_length = params_.path_planning.path_shift.minimum_shift_length;
shift_params.minimum_shift_yaw = params_.path_planning.path_shift.minimum_shift_yaw;

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Could you also remove the parameter from the param, schema, and config directory as well?

@sonarqubecloud

Copy link
Copy Markdown

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

Labels

beta/v0.64 Base branch: beta/v0.64 diffusion_planner Product: diffusion_planner run:build-and-test-differential After beta/v0.41

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants