 | | Re: Extra RAM —John Barnes
| | | | (...) Ah! I think I see the difference. My concept of the "map" is something that starts out blank and the prime objective is to fill it in. I suspect the use of a term like "door" implies a map supplied from outside. In which case I agree that an (...) (24 years ago, 22-Jun-00, to lugnet.robotics)
| | | | | | | | | | Re: Extra RAM —Andy Gombos
| | | | | | I think now that either way could be implemented, with special software for the vector map. A bit map you can upload, and just view, but a vector map, you can save space, but when uploaded, you could easily have software to map out the area. The (...) (24 years ago, 22-Jun-00, to lugnet.robotics)
| | | | | | | | | | | | Re: Extra RAM —Carsten Müller
| | | | | (...) If you start with a blank map, you don't need a full sized array for mapping. You can build up a linked list or a binary Tree where each node hold position information status and size. If your memory is nearly use up. You start a garbage (...) (24 years ago, 23-Jun-00, to lugnet.robotics)
| | | | | | | | | | | | Re: Extra RAM —Andy Gombos
| | | | | To find doors, you can assume that they are are always on a wall. Then, to find an open door, use an edge finding algorithm to highlight the edges. Where there should be a wall, but is not, there must be a door. A closed door could be found by (...) (24 years ago, 23-Jun-00, to lugnet.robotics)
| | | | | | |
