-
Notifications
You must be signed in to change notification settings - Fork 647
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
[KAIST] Problem of running KAIST dataset enabling ZUPT. #90
Comments
same with u?also need help |
Are you able to enable gdb debug mode and see where this is failing. |
@WILBURNHUANG @sjlszz try to increase the threads. See #89 |
I don't think it's an issue in the'zupt' module. When i run kaist sequence 27 without zupt (speed goes to 0) the same error occurs as below line. And this is the gdb debug module. what's the problem?
|
The problem seems to happen on this function: select_imu_readings. From the debugging info, you select IMU reading in a 0.3s period. If your IMU measurements is published at 400HZ, you will select 0.3/(1/400)=120 IMU measurements, which might lead to the computation problem. That's my initial thought. Discussion is welcome. |
It seems that there are not enough IMU measurements to propagate with, thus is crashing. |
Can you please see if #117 fixes this issue for you? |
Hi, new to SLAM here and really appreciate this great work.
I'm trying to run with KAIST Urban 28. The data was loaded successfully and I followed the suggested setting (disable "skip stop section", Speed 2.00).
I used "pgeneva_ros_kaist.launch" as launch file.
The error is "terminate called after throwing an instance of 'std::out_of_range'
what(): vector::_M_range_check: __n (which is 18446744073709551615) >= this->size() (which is 2001)".
Can anyone give any suggestion?
The text was updated successfully, but these errors were encountered: