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

Wrong localization orientation in Autoware #79

Closed
lchojnack opened this issue May 23, 2024 · 4 comments
Closed

Wrong localization orientation in Autoware #79

lchojnack opened this issue May 23, 2024 · 4 comments
Assignees
Labels
type:bug Software flaws or errors.

Comments

@lchojnack
Copy link
Collaborator

The current AWSIM main branch causes wrong localization orientation in Autoware.
I think the issue could be caused by recent orientation changes in the sensor_kit_base_link child components.
More investigation is needed

Screenshot_20240523_122322

@lchojnack lchojnack added the type:bug Software flaws or errors. label May 23, 2024
@lchojnack lchojnack moved this to Backlog in Autoware Labs May 23, 2024
@mozhoku
Copy link
Collaborator

mozhoku commented May 23, 2024

@lchojnack did you get this bug with default scene?

Could you try again after using the dynamic sensor placement tool.

Okay I got the same error. Looking into it.

This morning, when rebasing #71, I've noticed that the all transform values on the default vehicle prefab is 0, that might be the cause.

@mozhoku mozhoku self-assigned this May 23, 2024
@mozhoku mozhoku moved this from Backlog to In Progress in Autoware Labs May 23, 2024
@lchojnack
Copy link
Collaborator Author

@mozhoku Yes, I've get it on default scene without any changes.

@mozhoku
Copy link
Collaborator

mozhoku commented May 23, 2024

Okay found the reason.
When importing the sensor configuration with the dynamic sensor importing tool, the "velodyne_top_base_link" transform gets ~(-90°) rotation on Y axis. After defaulting it to it localizes properly.

Sorry for the trouble. I'll fix it in a separate PR since I'm the one who merged it.

@mozhoku
Copy link
Collaborator

mozhoku commented May 24, 2024

Opened a PR for this issue in autoware_individual_params repo:
- autowarefoundation/autoware_individual_params#51

After looking into this with @xmfcx he noticed that top lidars Frame ID is "sensor_kit_base_link". We will change this ID to "velodyne_top_base_link".

@mozhoku mozhoku closed this as completed May 24, 2024
@xmfcx xmfcx moved this from In Progress to Done in Autoware Labs May 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Software flaws or errors.
Projects
No open projects
Status: Done
Development

No branches or pull requests

2 participants