We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
currently origin of laser scan is baselink but it's origin should be a position of lidar
consider origin of lidar position and fusion laserscans for each if multilidar is available
implement to improve laser scan
The text was updated successfully, but these errors were encountered:
this issue is solved by #624
Sorry, something went wrong.
chore(imu_monitor): change yaw_rate_diff_threshold from 0.14 to 0.18 (a…
281b6ed
…utowarefoundation#582) Signed-off-by: Tomohito Ando <tomohito.ando@tier4.jp>
feat(planning_launch): add config for regulate lane change (autowaref…
b7dc59e
…oundation#582) Signed-off-by: Fumiya Watanabe <rej55.g@gmail.com>
Merge pull request autowarefoundation#582 from tier4/sync-awf-latest
8501a52
chore: sync awf-latest
No branches or pull requests
Checklist
Description
currently origin of laser scan is baselink but it's origin should be a position of lidar
Purpose
consider origin of lidar position and fusion laserscans for each if multilidar is available
Possible approaches
Definition of done
implement to improve laser scan
The text was updated successfully, but these errors were encountered: