[C++][Python][Major] Replaced the way collisions and visuals are stored in...
[C++][Python][Major] Replaced the way collisions and visuals are stored in GeometryModel. Now it is two lists of GeometryObject (one for collisions, one for visuals) aggregating information instead of multiple vectors. Now handle multiple collisions/visuals for one link when parsing urdf file and keep track of the mesh absolute path. Changed binding accordingly.
Showing
- CMakeLists.txt 1 addition, 0 deletionsCMakeLists.txt
- src/algorithm/collisions.hpp 11 additions, 6 deletionssrc/algorithm/collisions.hpp
- src/multibody/geometry.hpp 209 additions, 23 deletionssrc/multibody/geometry.hpp
- src/multibody/geometry.hxx 99 additions, 46 deletionssrc/multibody/geometry.hxx
- src/multibody/parser/urdf-with-geometry.hpp 8 additions, 5 deletionssrc/multibody/parser/urdf-with-geometry.hpp
- src/multibody/parser/urdf-with-geometry.hxx 47 additions, 20 deletionssrc/multibody/parser/urdf-with-geometry.hxx
- src/python/geometry-data.hpp 8 additions, 3 deletionssrc/python/geometry-data.hpp
- src/python/geometry-model.hpp 32 additions, 17 deletionssrc/python/geometry-model.hpp
- src/python/geometry-object.hpp 95 additions, 0 deletionssrc/python/geometry-object.hpp
- src/python/python.cpp 3 additions, 1 deletionsrc/python/python.cpp
- unittest/geom.cpp 8 additions, 8 deletionsunittest/geom.cpp
Loading
Please register or sign in to comment