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

Question about time performance #13

Open
wwtinwhu opened this issue Dec 26, 2024 · 0 comments
Open

Question about time performance #13

wwtinwhu opened this issue Dec 26, 2024 · 0 comments

Comments

@wwtinwhu
Copy link

wwtinwhu commented Dec 26, 2024

Hello, @kevin2431 !

Thanks for your open-sourced and excellent work!

I tested your refactoring code with r3live_dataset-hku_campus_seq_00.bag. I turned off the visualization and changed some parameters (ds_size, voxel_size and max_voxel_num). On this dataset, the average frame processing time is around 80 ms. While as shown in your paper, your method (segment=1, with marginalization) time is 49.7 s on the NYA01 (395 s). And the average frame processing time is around 13 ms. So is it normal for my test? Do you have any suggestions to speed up the processing time? Here is my CPU and parameter setting.

CPU
Intel® Core™ i7-14700K × 28

trajectory:
init_interval: 3e8
seg_interval: 4e7
seg_num: 3
kinematic_constrain: 2.0
init_pose_weight: 1e9
converge_thresh: 0.001
max_iterations: 25

mapping:
ds_size: 2.0
voxel_size: 1.0
max_voxel_num: 10
planer_thresh: 0.1
max_range: 120
min_range: 1

Thank you in advance for your help!

Best regards,
Weitong Wu

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

No branches or pull requests

1 participant