Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Smart mapping for robots exploring huge areas! 🗺️ This is called Rolling-Bonxai. When a drone or ground robot maps a massive area, say a whole city or massive warehouse, storing the entire map in memory gets expensive fast. You run out of RAM. This solution is simple, only keep...

15,711 Aufrufe • vor 4 Monaten •via X (Twitter)

8 Kommentare

Profilbild von Inspector fomo
Inspector fomovor 4 Monaten

Rolling-Bonxai trades full-map RAM for disk I/O latency on reloads. That mirrors the sim-to-real transfer bet I wrote about last month. The real test is whether chunk swaps stay fast enough for continuous locomotion.

Profilbild von Chandra Shekhar 📟
Chandra Shekhar 📟vor 4 Monaten

Where do you keep on finding banger upon banger codes and papers in robotics? Do you taste like the sauce because you are dipped in the sauce? Or is it because you know where to find the best sauce?

Profilbild von Damir Wallener
Damir Wallenervor 4 Monaten

Chunked voxel grid. Watch for… - boundaries -> thrashing -> planning stalls - integration errors -> drift -> can’t find right chunks - map fragmentation -> loop closure -> ghosting - alt/range est. errors -> scale drift -> matching failures It’s simple until it meets the real world. 🙂

Profilbild von MendysRobotics
MendysRoboticsvor 4 Monaten

Sliding-window maps are the pragmatic answer for warehouse-scale AMRs too - you rarely need the full global map in RAM, just local occupancy plus anchors for loop closure. Curious how Rolling-Bonxai handles loop closure corrections once old chunks are already on disk.

Profilbild von Juan Jimeno
Juan Jimenovor 4 Monaten

@facontidavide check this out

Profilbild von Geospatial FM
Geospatial FMvor 4 Monaten

That’s what they’ve always done with computer games

Profilbild von WanderingDuck
WanderingDuckvor 4 Monaten

Your data is too dense. If the space is rectilinear just use a line and width and height.

Profilbild von Johannes Tscharn
Johannes Tscharnvor 4 Monaten

Quite interesting how we developed solutions to these kinds of problems in video games.

Ähnliche Videos

researchers gave a tiny local model human-style memory and its context limit basically stopped existing a team from MBZUAI, Princeton and Weizmann took a 1B model and rebuilt how it reads. instead of attending to everything at once, the model reads in 1,024 token chunks and passes the important stuff forward through an associative memory, the same way you carry the plot of a book between chapters without rereading them. the design mirrors human memory on purpose. full attention inside a chunk works as short-term memory. the module that carries information between chunks works as long-term memory. they even trained it like a person, starting with short easy texts and raising the difficulty gradually, because memory thrown into the deep end learns nothing. the numbers back it up. the normal model burns 40GB of GPU memory on a long document and collapses hard past its limit, dropping from 0.86 to 0.32 accuracy. the memory version holds 0.71 at double that length while using a flat 12GB no matter how long the input gets. it also needs about 30% fewer FLOPs. the part i keep thinking about is that nobody scaled anything here. they didn't build a bigger model, didn't stretch the window, didn't add compute. they looked at how a brain handles a long day and copied the architecture. a model small enough to run on a consumer gpu now survives documents its own architecture used to choke on. we keep treating intelligence as a compute problem. sometimes it's a memory problem.

Alex Veremeyenko

16,147 Aufrufe • vor 3 Monaten