Robotics-lab6-tasks

Robotics Main Page > Lab 6 Tasks

---

Robot Group (Nick B, James, Thomas, Nick C)

• Next Meeting: Monday at 8pm
• Tasks
  • Design robot
  • Decide how to divide work of building robots
  • Build robots
• Completed:

                      Two bots, each travels in one dimension with the motor in PORT_A.
                      The bots have a sensor tower with four compasses at the 'Front'
                      and the motor at the 'Back'. The compass pointing towards the
                      'Front' is in PORT_1 and the rest go clockwise. So the one to the
                      'Right' is in PORT_2 and so on.

Software Group (Nick M, Sam, David, Dylan)

• Next Meeting: Tuesday 8:00 AM (Communicating via email)
• Tasks
  • Due Monday: Magnetic Mapper code v1.0
    • Respond to key input (done)
      • This is not implemented ideally. Currently one press starts the robot moving and the next press stops it instead of the robot moving only while the key is held down
    • Implement motor functionality (done)
    • Collect data
      • Sensor IDs (done)
      • Timestamp
      • Room ID
      • Coordinates
        • (x,y) by tile
      • Expected Sensor Data (done)
      • Actual Sensor Data
    • Using Brad's function, write data to CSV file.

Testing/Automation/Refactoring Group (Aaron, Nick C, Dylan, Brad, Gil)

• Descriptions: Testing, Automation, Editing/Refactoring
• Next Meeting: ?
• Tasks
  • Test magmapper.py
    • Due Date: Tuesday at 8am
    • Owner(s):
    • Subtasks
      • Make sure documentation is clear (DONE)
      • Write a script to ensure each line of code in magmapper.py is tested
  • Test nxt_common.py
    • Due Date: Tuesday at 8am
    • Owner(s): Aaron
    • Subtasks
      • Make sure documentation is clear
      • Write a script to ensure each line of code in nxt_common.py is tested
  • Test record_data_lib.py
    • Due Date: Tuesday at 8am
    • Owner(s):
    • Subtasks
      • Make sure documentation is clear
      • Write a script to ensure each line of code in record_data_lib.py is tested
  • Compass Sensor Calibration Test (DONE)
    • Due Date: Monday at 8pm
    • Owner(s): Dylan, Gil
    • Purpose: Do compass sensors calibrate differently? NO Are some more likely to calibrate inaccurately or imprecisely? NO
  • Compass Sensor Interference Test (DONE)
    • Due Date: Monday at 8pm
    • Owner(s): Gil
    • Purpose: Do compass sensors interfere with each other when placed close together?
    • Results: Placing the sensors as closely as possible to each other, Gil found no interference.

Environment Preparation Group (Brad, Patrick)

• Next Meeting: ?
• Tasks
  • Determine Room Dimensions
    • Due Date: Tuesday at 8am
    • Owner(s): Patrick
    • Results
      • D128 - 22 x 28 (EW x NS)
      • D129 -
      • D124 - 24 x 28 (EW x NS)
  • Mark off origin, quadrants, and regular periodic difference
    • Digitally make note of "unreadable" tiles, i.e. ones with something immovable on them
    • Due Date: Tuesday at 8am
    • Owner(s): Patrick

Data Collection Group (Michael, Tristan, Gil)

• Next Meeting: Tuesday at 8am
• Tasks

Data Synthesis Group (Brad, Patrick)

• Next Meeting: ?
• Tasks
  • Identify inaccessible tiles via a CSV file
  • Create a python function for use by the software group that will create a correctly formatted entry in a CSV data file ( Done 4/3 )
  • Create software to visualize a CSV data file in graphical map form
• Resources
  • Working with Lab 6 Data

Documentation/Writeup Group (Aaron, Jeremy, Gus)

• Next Meeting: ?
• Tasks
  • Overview
  • Description of Robot
  • Description of Environment
  • Description of Software
  • Description of CSV file
  • Procedure
  • Pictures of Robot
  • Attach Python scripts as appendices
  • Attach CSV files as appendices
  • Attach environment maps as appendices

Leading/Organizing Group (Jeremy, Sam, Aaron)

• Next Meeting: ?
• Tasks
  • Make sure everyone has a task at any given point
  • Make sure work is being distributed as evenly as possible
  • Make sure tools are being used (correctly) by everyone (wiki, github)
  • Make sure standards are defined where appropriate
  • Make sure standards are being met
  • Understand the dependencies between groups