nordp/tda593

The goal of this course project is to model a robotic system with various UML-based modeling techniques, and implement a simple demonstrator of such a system.

TDA593

The goal of this course project is to model a robotic system with various UML-based modeling techniques, and implement a simple demonstrator of such a system.

tda593's Issues

Enforce "one robot per room" constraint in conductor

Strategies

Implementation of strategies. (e.g 'Shortest path' etc...)

More information about Walls and enivoriment

Right now you cannot know if the wall is vertical or horizontal. This is an issue since then printing out the map would be difficult since you cannot know if you are supposed to "loop" trough the the wall or not since you cant really say when it "end".

Conductor Mission feed

Handle distribution of mission points to various robots.

Implement collisionprevention routine

Since you're already on it

System currently depends on time to tell when robot leaving physical area has left

The conductor currently waits 2 seconds before marking an area as unoccupied, but it may take longer for a rover to leave the area. Especially if it's heading towards another occupied area, which may make it wait indefinitely.

Telling a robot to move slightly often results in it getting stuck in "spin"

Moving 1-2 coordinate units have caused this behaviour, can be avoided by traversing larger steps.

Implement RobotFailure routine

This will have to have a fake trigger as there currently is no way for the robot to have a failure

Implement single robot navigation

What it says on the tin

Make coordinate conversion in simulator robot

Right now there is an ugly conversion in the get coordinate method that works, this should be refactored and extended to the goTo method.

Add areas to map

Suggestion:
^: physical
*: logical
¨: both

Check for valid ids in the operator interface

Break out map printing to its own class

(master) nullpointer / exception in thread

When starting the simulator through the command line, after a while the following exception is thrown:

Exception in thread "Thread-9" java.lang.NullPointerException
at control_station.PointRewarder.run(PointRewarder.java:45)
at java.lang.Thread.run(Thread.java:748)

Collision prevention could use some touch-up

Currently, collision prevention just makes the robots slower when moving through each other.

Area.isInArea(Coordinate coord) is broken

Which makes enforcing of physical room limits difficult

Store gps sensor data in status in robot controller

Implement Object.equals(Object o) on Instruction

Point rewarder does not notify the conductor about strategy.

IF we are supposed to implement the strategy "maximize reward points", the conductor needs to know the current reward procedure, which is not currently available to the conductor.

"Some tests should be done"

Creation of Environment

Setup of the room structure for the hospital setting. (Both logical and physical).