-
Notifications
You must be signed in to change notification settings - Fork 1
To Do List
Matheus Vieira Portela edited this page Apr 1, 2014
·
57 revisions
Camera:
- Write Kinect node
- Create communication system for transmitting RGBD images
Dummy Camera:
- Transmit only one frame for testing purposes
- Record test video from Kinect (both image and depth)
Vision:
Strategy:
- Get real information from Vision or Simulation as soon as they are created
- Create game states (running, paused, field kick, goal, etc)
- Create constants configuration file, to be used by all nodes
Simulator:
- Find out why the ball sinks through the ground sometimes
- Lower the gravity center of the robots so that they don't move over time
Documentation:
Gabriel:
- Start writing vision system with dummy_frame and the old code
Tcholas:
- Start writing simulation system
Ícaro:
- Simulation: Create a simulation node, which will have a Gazebo plugin for controlling the robots and publish the state of the simulation
Dummy Camera:
- Create the dummy_camera node, which loads a video file and publishes it on the /camera/raw_image topic
- Create the dummy_frame node, which loads a video file and publishes its second frame on the /camera/raw_image topic
- Get image from Dummy Camera
- Dummy Camera: Create test for the dummy_camera module, which prints the images transmitted on the screen
Vision:
- Create vision node, which will subscribe to the camera topic, process the image, and publish important information about the robots, the ball, and the game in general (e.g. "/vision/robots_info")
Strategy:
- Create strategy node, which will subscribe to either the vision topic or the simulation topic and define the robots behaviour, publishing velocities in a topic (e.g. "/strategy/robots_velocities")
Simulator:
- Model the field, the robot, and the ball on Gazebo SDF files
Documentation:
- Write unit test section in the Development Guidelines
- Write about the messages for the project