This is a fascinating project but offering much help with the code probably means you're going to need to go into more detail about your requirements and your current codebase.
My questions, offhand:
- How large and what shape is the detection area for the Roomba?
- How exactly are the objects generated and what forms do they take?
- Is the simulated Roomba allowed to pass through the obstacles?
- How "stupid" do you want the Roomba to be about things like the size and shape of the room and obstacles?
- How do you want the Roomba to move through the room? Should it prioritize vertical paths over horizontal? When it finds an object, should it try to discover the entirety of the object or should it try to get back to the original path? What if there are regions that are theoretically unobstructed but which the Roomba is too "large" to enter?
My thoughts on solutions:
- Decide on a plan for how the Roomba should move in an unknown environment and when it encounters obstacles. For example, choose to move vertically until an object is found, then (assuming a collision should redirect the Roomba) have the Roomba follow the outline of the object clockwise until it reaches the original position again, at which time it should move to the other side of the object and continue scanning up and down.
- Have the detection logic work as follows: the Roomba is in position (x,y) (assume there aren't already obstacles in detection range). First, it attempts to move to position (x+1,y). The program then verifies that no obstacles are inside range. If so, it attempts to move to (x+2,y). If there is an obstacle in detection range, the Roomba's position again becomes (x,y) and the detected position of the obstacle is recorded.
- Rather than trying to reduce the size of the stored obstacles by storing them in a small matrix like that (which I assume contains the coordinates for two corners of a rectangle or a corner, length and height) let the detected obstacles appear in a matrix like they would on a map.
I've drawn out what I mean by 2 and 3 below:
Move 1:
% Room map
***********************************************
* *
* *
* ***** *
* * A * *
* ***** *
* *
* [] * % The Roomba is two row from impacting A
* * % and is at position (x,y)
***********************************************
% Search map
***********************************************
* *
* *
* *
* *
* *
* *
* [] * % the Roomba knows nothing
* *
***********************************************
Move 2:
***********************************************
* *
* *
* ***** *
* * A * *
* ***** *
* [] *
* * % The Roomba is one row from impacting A
* * % at position (x+1,y)
***********************************************
Move 3:
% Room map
***********************************************
* *
* *
* ***** *
* * A * *
* []*** *
* *
* * % The Roomba impacts A
* * % at position (x+2,y)
***********************************************
***********************************************
* *
* *
* ***** *
* * A * *
* ***** *
* [] *
* * % The Roombra is moved back to position (x+1,y)
* *
***********************************************
% Search map
***********************************************
* *
* *
* *
* *
* ** *
* [] *
* * % Data about the impact is added
* * % to the output map
***********************************************
Move 4:
***********************************************
* *
* *
* ***** *
* * A * *
* ***** *
* [] *
* * % The Roombra is moved to position (x+1,y-2)
* * % to get around what it has seen of the obstacle
***********************************************
