You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@koide3
I met the problem that interactive slam was killed when I am loading a new map about '1GB' that was dumped from hdl_graph_slam
So, I am wondering what in essence decides the size of map that interactive slam can load up to? And may I have your advice on how to solve this problem
(Also, this happens after the load map progress went to 100%)
I put the terminal output below for your convenience:
@koide3
I met the problem that interactive slam was killed when I am loading a new map about '1GB' that was dumped from hdl_graph_slam
So, I am wondering what in essence decides the size of map that interactive slam can load up to? And may I have your advice on how to solve this problem
(Also, this happens after the load map progress went to 100%)
I put the terminal output below for your convenience:
jeremy@jeremy-Latitude-9420:~/Documents$ rosrun interactive_slam interactive_slam
construct solver: lm_var_cholmod
Using CHOLMOD poseDim -1 landMarkDim -1 blockordering 1
done
construct solver: lm_var_cholmod
Using CHOLMOD poseDim -1 landMarkDim -1 blockordering 1
done
loading pose graph...
nodes : 4840
edges : 4839
kernels: 0
anchor_node:1
anchor_edge:1 - 0
4839 : num_points 13576, stride 32
4838 : num_points 13671, stride 32
4837 : num_points 13783, stride 32
4836 : num_points 13626, stride 32
4835 : num_points 13690, stride 32
.
.
.
.
2784 : num_points 16367, stride 32
2783 : num_points 16194, stride 32
2782 : num_points 16090, stride 32
2781 : num_points 12242, stride 32
Killed
The text was updated successfully, but these errors were encountered: