List of tasks needs to be done

From Earlham CS Department
Revision as of 16:58, 23 November 2012 by Mmludin08 (talk | contribs) (→‎Test simulation and robot and make plans for next week)
Jump to navigation Jump to search

SC12 Week

2 hours: Add function for wireless network communication to the my_swarm.cc file

1 hour: Fix the obstacle avoidance function

1 hour: simulation testing

Thanks Giving Break Week

Readings --> (done)

  • Monday 1-2hour: Read the User Manual for the latest version of Player/Stage
  • Monday 1 hour: Paper "The Player/Stage Project: Tools for Multi-Robot and Distributed Sensor Systems" by the player/stage developers
  • Monday 1 hour: review online manual for writing player stage controller

Create Makefile -->(done)

  • Tuesday 30 minutes: write a Makefile for the controller using example from the User Manual

Fix environment (world - my_swarm.world) file -->(done)

  • Tuesday 2-3 hours: Increase the number of swarm in the .world file. This take while sometime because of adjusting the position of the robot. It will be cool to write control function to randomly spread the robots in the defined area.
  • Tuesday 1 hour: Decrease the size of the robots to make it easy for increased swarm to search for target and avoid obstacle collision (done)

Fix the Configuration (my_swarm.cfg) file -->(done)

  • Tuesday 1 hour: Add drivers for instantiating new robots added to the .world file
  • Tuesday 1 hour: Config their Navigational and obstacle avoidance drivers

Test simulation:

  • Wednesday 20 minutes: Test robot behavior and environment
  • Wednesday 10 minutes: robot obstacle avoidance
  • Wednesday 20 minutes: communication
  • Wednesday 30 minutes: Planes for what needed to be work on Next week related to software

Wednesday 2-3 hours: Edit the Documentation for the project (done 70%)

Wednesday 2-3 hour: work on the final paper and expand on the software part

Working on the first draft of final paper

  • Thursday 3 hours: Re-reviewing literature studied over the course of semester
  • Friday 3-4 hours: Writing introduction, and literature review.
  • Friday 1-2 hours: Software description
  • Saturday 2 hours: backward reading the so far written first draft
  • Saturday 1-2 hours: making necessary changes based on the backward reading
Retrieved from "https://wiki.cs.earlham.edu/index.php?title=List_of_tasks_needs_to_be_done&oldid=13880"