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
Applying the patch below to the octomap shows that the octomap contains a lot of "invalid handles". This is surely not very efficient, and it would be better if these were never placed in there, to begin with.
--- a/opencog/timeoctomap/TimeOctomap.cc
+++ b/opencog/timeoctomap/TimeOctomap.cc
@@ -80,14 +80,19 @@ Handle TimeSlice::get_atom_at_location(const point3d& locati
point3d_list TimeSlice::get_locations(const Handle& ato)
{
point3d_list pl;
+std::cout<<"duuude getting locations at slisece="<<t<< " p="<<((void*)this)<<st
for (AtomOcTree::tree_iterator ita =
map_tree.begin_tree(),
end = map_tree.end_tree();
ita != end;
++ita)
{
+std::cout<<"duuude looopy atom="<<ita->getData()<<std::endl;
if (ita->getData() == ato)
+ {
+std::cout<<"duuuude yayyyy"<<std::endl;
pl.push_back(ita.getCoordinate());
+ }
}
return pl;
}
Applying the patch below to the octomap shows that the octomap contains a lot of "invalid handles". This is surely not very efficient, and it would be better if these were never placed in there, to begin with.
prints this:
The text was updated successfully, but these errors were encountered: