There is not much interactions between hbot maps and luabot, maps are rather objects that you feed to map generators, and you connect a sensor to a map generator. More...
Classes | |
| class | GridMap |
| Basic map; usually for simple map generation without SLAM. More... | |
| class | SmartMap |
| Evolution of GridMap, with copy-on-write and nice memory-efficient structure in case of several copies of a map; use it when you often need to derive one map from another. More... | |
| class | SlamMap |
| This is a special map, acting as an umbrella for SLAM-enabled maps; actually several maps are generated by the SLAM algorithm everytime a step of generation is called, and this map represents the "best-rated" map of the set. More... | |
| class | VectorialMap |
| This is a vectorial map, defining the empty space as a polygon; really useful for efficient pathfinding (TRA*). More... | |
| class | MapGenerator |
| Generates a grid map thanks to area sensor reports; it create the grid by filling all the cells corresponding to the area concerned by the sensor scan, i.e. More... | |
| class | MapRaytracer |
| Generates a grid map thanks to area sensor reports; it create the grid by tracing rays on the map, corresponding to sensor records in a report, i.e. More... | |
| class | SlamGenerator |
| Generates a probable grid map thanks to area sensor reports; SlamGenerator actually creates a set of maps (stored in one SlamMap instance) with small variations around the robot position and sensor reports. More... | |
| class | OccupancyMapGenerator |
| Generates a grid map thanks to robot's moves: where the robot goes, the map is set to clear. More... | |
There is not much interactions between hbot maps and luabot, maps are rather objects that you feed to map generators, and you connect a sensor to a map generator.
But more bindings should follow soon.
1.6.1