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

feat(awsim_sensor_kit_launch): awsim load concatenate node parameters #25

Merged

Conversation

vividf
Copy link
Contributor

@vividf vividf commented Nov 7, 2024

Description

PR autowarefoundation/autoware.universe#8300 introduces a new concatenate algorithm and also removes the default parameter, thus the launcher would need to load the parameter from the parameter file.

Pre-review checklist for the PR author

The PR author must check the checkboxes below when creating the PR.

In-review checklist for the PR reviewers

The PR reviewers must check the checkboxes below before approval.

Post-review checklist for the PR author

The PR author must check the checkboxes below before merging.

  • There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

@vividf vividf changed the title feat: awsim load comcatenate parameter feat(awsim_sensor_kit_launch): awsim load concatenate node parameters Nov 8, 2024
@vividf vividf marked this pull request as ready for review November 8, 2024 04:31
@vividf vividf self-assigned this Nov 8, 2024
@SakodaShintaro
Copy link
Contributor

Thank you. I will confirm e2e_simulator.

Copy link
Contributor

@SakodaShintaro SakodaShintaro left a comment

Choose a reason for hiding this comment

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

e2e_simulator works correctly.

I have a concern about changing the timeout_sec parameter from 0.01 to 0.2. While this change could affect the behavior of autoware_ekf_localizer, I haven't observed any issues on my machine. I would like to spend more time testing this change.

@vividf
Copy link
Contributor Author

vividf commented Nov 8, 2024

@SakodaShintaro

I see, I understand your concern.
I think you can test with the timeout sec: 0.05 or even lower in the simulation environment.

@vividf vividf requested a review from SakodaShintaro November 8, 2024 07:51
Copy link
Contributor

@SakodaShintaro SakodaShintaro left a comment

Choose a reason for hiding this comment

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

Thank you for the correction.
LGTM

Copy link
Contributor

@SakodaShintaro SakodaShintaro left a comment

Choose a reason for hiding this comment

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

@vividf
I think a corresponding pull request is needed in https://github.com/autowarefoundation/autoware_individual_params.
For now, I will temporarily stop this pull request.
(Please tell me if I'm mistaken)

@vividf
Copy link
Contributor Author

vividf commented Dec 2, 2024

@SakodaShintaro
You are right :)
The parameters are moved in this PR autowarefoundation/autoware_individual_params#54.
Could you help test this PR with the individual PR together on the awsim :)
Thanks for your support!

Update!!!
This is not needed so I reverted the changes

@vividf vividf requested a review from SakodaShintaro December 2, 2024 08:11
@vividf vividf force-pushed the feature/tier4_awsim_load_concatenate branch from 2f2f4aa to 01f20e8 Compare December 3, 2024 02:56
@vividf
Copy link
Contributor Author

vividf commented Dec 3, 2024

@SakodaShintaro
Sorry that the changes are not necessary, so I reverted the changes.

@SakodaShintaro
Copy link
Contributor

@vividf
I merged the two PRs

into autoware:main on my machine and ran e2e_simulator with AWSIM, which has 3 lidars (top, left, and right).
However, Autoware could not engage due to LiDAR flickering.

simplescreenrecorder-2024-12-09_13.53.49.mp4

The multi LiDAR AWSIM is available to TIER IV employees only. link

Could you please confirm this?

@vividf
Copy link
Contributor Author

vividf commented Jan 21, 2025

As discussed in the internal link, the issue occurred due to unstable timestamps from the sensors.

For AWSIM, the timestamps of the three LiDARs should be stable (as they are in AWSIM Lab), so this should ideally be fixed within AWSIM. However, since the timestamps are currently unstable, I will temporarily set the noise window to a larger value.

Once this issue is resolved, you can create another PR to revert it to a lower value.

@vividf
Copy link
Contributor Author

vividf commented Jan 21, 2025

@SakodaShintaro
Note that the new concatenate algorithm PR is merged, so this PR should be merged asap :)
Thanks a lot for your help!

Copy link
Contributor

@SakodaShintaro SakodaShintaro left a comment

Choose a reason for hiding this comment

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

@vividf
Thank you very much!

I have tested this PR in single LiDAR AWSIM, and it works well.

In 3 LiDARs AWSIM, there was still flickering at time scale = 1.0, but it worked well when the time scale was lowered. I'll deal with this for now.

@SakodaShintaro SakodaShintaro merged commit 33ef7ee into tier4:main Jan 21, 2025
6 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants