Memory aware management keeps dense maps on small robots working
Memory-Aware Keyframe Management for Dense Maps on Memory-Constrained Robots
Robotics
Summary
When small robots try to run both a language model and keep a detailed 3D map, they can run out of memory because both use the same storage space. The authors propose a way to carefully control how much memory the map uses by limiting it directly instead of just limiting the number of map snapshots, which can vary greatly in size. They group map information by meaningful spaces like rooms and corridors, keeping only the areas the robot is in or about to enter. This lets the robot avoid crashes and still localize itself more accurately compared to other methods.
What this means in practice
- •For mobile robot developers: Build robots that can run 3D mapping and language models together on memory-limited embedded devices without running out of memory.
- •For indoor robot navigation teams: Improve localization accuracy by managing map memory according to rooms and corridors rather than just counting frames.
Authors
Huichang Yun, Jaeyeul Kim, Seungho Yoo
Abstract
Running a language model and a dense 3D map on one device means the two share one memory, and exceeding its limit is an out-of-memory failure. Map systems that keep a bounded working set bound it by a count of keyframes, but the memory one keyframe occupies varies widely with what it carries, so a count does not control what the working set occupies. The unit of admission is as poorly matched, since a radius around the pose, a fixed cell, or the graph neighbors of the last matched keyframe all move parts of the map that are not needed. We therefore propose two decisions. First, the memory the resident map uses is bounded directly, and the cost of every admission is known before any data is read, from per-keyframe resident sizes computed offline and carried with the map. Second, keyframes are admitted and released at a semantic spatial unit, the rooms and corridors of the building, so that the robot holds the zone it occupies together with the zone it is about to enter while the zones it has passed are released. Every admission measures the resident total, makes room, and only then reads, so the budget is never overshot. On two NVIDIA Jetson boards the budget holds in every run and the model gives up at most 0.8 percent of its throughput, whereas without it the operating system kills the model or the map. Under that budget, and over the environments evaluated, admission by semantic zone localizes 6-9 points more of the query frames than a geometric partition of matched zone count and about twice as much as the retrieval of RTAB-Map, at a lower ATE. Bounding memory lets the map and the model coexist, and moving the map in semantic zones makes the bounded map usable.