-
Notifications
You must be signed in to change notification settings - Fork 701
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
fix: add select option for dynamic transform lookup time #10288
base: main
Are you sure you want to change the base?
fix: add select option for dynamic transform lookup time #10288
Conversation
Signed-off-by: badai-nguyen <dai.nguyen@tier4.jp>
Thank you for contributing to the Autoware project! 🚧 If your pull request is in progress, switch it to draft mode. Please ensure:
|
CI error:
I think this will be passed after autowarefoundation/autoware_utils#50 merged |
As here any reason to let user select to pick the latest or message time? I thing using message time is the only option to be. Proposal: do not add option |
managed_tf_buffer_ = | ||
std::make_unique<autoware_utils::ManagedTransformBuffer>(this, has_static_tf_only_); | ||
managed_tf_buffer_ = std::make_unique<autoware_utils::ManagedTransformBuffer>( | ||
this, has_static_tf_only_, use_pc_stamp_for_dynamic_transform_lookup_); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same comment with taekjin-san.
Do we need transform within current timestamp for pointcloud transforms? If no, we can simply set true in this part.
The |
Those can be co-exist. |
Description
Related links
Parent Issue:
How was this PR tested?
static_map_loader
mode: https://evaluation.tier4.jp/evaluation/reports/03eefbbe-e4d9-5ef6-a0f4-363591d32cec?project_id=prd_jtdynamic_map_loader
mode: https://evaluation.tier4.jp/evaluation/reports/2245262f-959f-50a9-8afc-177008b258c4?project_id=prd_jtNotes for reviewers
None.
Interface changes
None.
Effects on system behavior
None.