###Repository for TeamThree AVC
- Tim - Hardware Development - Developing and building Chassis, working to integrate sensor components and testing hardware
- Sean - Project Lead/Documentation - Organising meetings and progress reports, documenting work against goals.
- Eli - Software Testing - Working with Software Development people, testing cases and network implementation.
- Jaimar - Software Development - Writing main methods code and extending code based on testing
- Callum - Software Development - Writing main methods code and extending code based on testing
###Week 1 Checklist:
- Sean: Signed plan and finish documentation GitHub setup
- Tim: Assemble Pi and relevant hardware, prototype chassis
- Jaimar: Develop code for basic movement
- Callum: Develop code for basic movement
- Eli: Establish SSH and research Network commands
###Week 1 Review:
- Sean: Signed plan and finish documentation GitHub setup
- Tim: Assemble Pi and relevant hardware, prototype chassis
- Jaimar: Develop code for basic movement
- Callum: Develop code for basic movement
- Eli: Establish SSH and research Network commands
- All goals were acclompished
- Github is set up and read for use
- All members attended the lab
- All members submitted their reviews
###Week 2 Checklist:
- Sean: Plan next weeks and meeting, add to GitHub documentation and reviews
- Tim: Develop chassis/Finalise
- Jaimar: Suggest ways to develop code and begin movement code
- Callum: Suggest ways to develop code and begin movement code
- Eli: Test code and get gate opening
###Week 2 Review:
- Sean: Signed plan and finish documentation GitHub setup
- Tim: Assemble Pi and relevant hardware, prototype chassis
- Jaimar: Develop code for basic movement
- Callum: Develop code for basic movement
- Eli: Establish SSH and research Network commands
- All goals were acclompished
- All members attended the lab
- All members that could attended the meeting
- We got the gate open!
###Week 3 Checklist:
- Sean: Update GitHub, plan meetings and reviews, help on coding
- Tim: Printing and designing parts
- Jaimar: Start traversing the line
- Callum: Start traversing the line
- Eli: Planning and developing code, future methods
###Week 3 Review:
- Sean: Update GitHub, plan meetings and reviews, help on coding
- Tim: Printing and designing parts
- Jaimar: Start traversing the line
- Callum: Start traversing the line
- Eli: Planning and developing code, future methods
- All goals were acclompished
- All members attended the lab
- All members that could attended the meeting
###Week 4 Checklist:
- Sean: Research and develop Quadrant 1 code with PID
- Tim: 3D printing done
- Jaimar: Complete Quadrant 1 code
- Callum: Complete Quadrant 1 code
- Eli: Research and develop Quadrant 1 code with PID
###Week 4 Review:
- Sean: Research and develop Quadrant 1 code with PID
- Tim: 3D printing done
- Jaimar: Complete Quadrant 1 code
- Callum: Complete Quadrant 1 code
- Eli: Research and develop Quadrant 1 code with PID
- All members attended the lab
- All members that could attended the meeting
- Sean and Eli switched with Jaimar and Callum
- We got the robot registering the line!
###Week 5 Checklist:
- Sean: Update and comment code, organise next weeks meeting/Logic behind 90* turns
- Tim: Lowering camera/Changing wheels/IR sensors
- Jaimar: Getting Pi to turn in relation to PID
- Callum: Getting Pi to turn in relation to PID
- Eli: Debugging and formatting code, writing to Pi
###Week 5 Review:
- Sean: Wrote the 90 turns and got them working
- Tim: Succesfully modified Pi
- Jaimar: Established smoother movement
- Callum: Established smoother movement
- Eli: Helped with coding and debugging
- All members attended the lab
- All members that could attended the meeting
- Sean and Eli switched with Jaimar and Callum
- We got the robot registering the line!
###Week 6 Checklist:
- Sean: Update and comment code, organise next weeks meeting/Quadrant 3 logic
- Tim: Printing off IR sensors/Battery pack
- Jaimar: Getting Pi to turn in relation to PID
- Callum: Getting Pi to turn in relation to PID
- Eli: Helped with additional coding
###Week 6 Review
- Sean: Update and comment code, organise next weeks meeting/Quadrant 3 logic
- Tim: Printing off IR sensors/Battery pack
- Jaimar: Getting Pi to turn in relation to PID
- Callum: Getting Pi to turn in relation to PID
- Eli: Helped with additional coding
- All members attended the lab
- All members that could attended the meeting
- We made more progress on getting the Pi moving
###Week 7 Checklist:
- Sean: Starting quadrant 3 code/logic
- Tim: Battery Pack/Advise on code
- Jaimar: Checking quads 1 and 2
- Callum: Checking quads 1 and 2
- Eli: Checking quads 1 and 2
- All members attended the lab that could
- All members that could attended the meeting
- All helped on sorting out code
- We got the robot registering up to the first T intersection
###Week 7 Review:
- Sean: Started quadrant 3 code
- Tim: Printed battery pack
- Jaimar: We sorted out quadrant 2 and 1
- Callum: We sorted out quadrant 2 and 1
- Eli: We sorted out quadrant 2 and 1
- All members attended the lab that could
- All members that could attended the meeting
Google Doc, Plan - https://docs.google.com/document/d/1B-4A15r7b_HlRaeunUikcQZN2YD_fXb_G-mnzb5xK0Q/edit?usp=sharing ###AVC Project Table
| Week | Dates | Team Objective(s) | Items Due | Conflicting Committments | Tasks |
|---|---|---|---|---|---|
| 1 | 18th April | Robot moving | AVC Plan Due | PHYS122 test | Week 1 Checklist |
| 2 | 25th April | Robot moving | ... | ... | Week 2 Checklist |
| 3 | 2nd May | Quadrant 1 complete | ... | ... | Week 3 Checklist |
| 4 | 9th May | Quadrant 1 complete | ... | COMP102 test | Week 4 Checklist |
| 5 | 16th May | AVC Progress report/Quadrant 2 | ... | ENGR121 test | Week 5 Checklist |
| 6 | 23rd May | Quadrant 3 | ... | ... | Week 6 Checklist |
| 7 | 30th May | Quadrant 4 | ... | ENGR101 test | Week 7 Checklist |
| 8 | 6th June | ... | ... | ... | Week 8 Checklist |
| 9 | 13th June | Submit final reports | Final report due | Exams | Week 9 Checklist |
###Weekly Progress Checklist
- How has each team member performed against their goal set last week?
- Have you set a goal for each team member for this/next week?
- Has the team discussed which tasks are the most important or urgent?
- Do any team members need more help to complete their assigned task(s)?
- Have you updated the task list on Github this week?
- Are all relevant code, bot photos and design files on the team Github?
- Have you noted which members attended labs and team meetings?
- Have team members shared their draft report sections (if the team decided they wanted to do that)?
- Are there any tasks that need to be done for progress to be made that have NOT been assigned to a team member?
Tim - Hardware Development - Developing and building Chassis, working to integrate sensor components and testing hardware. Contact details: Katharine Jermyn Hall 021 276 0270 tim.gastrell@gmail.com
Sean - Project Lead/Documentation - Organising meetings and progress reports, documenting work against goals. Contact details: msd.sean@clear.net.nz 022 628 3122
Eli - Software Testing - Working with Software Development people, testing cases and network implementation. Contact details: eli.tanoi@gmail.com 0277180697
Callum - Software Development - Writing main methods code and extending code based on testing Contact details: brigden.callum@gmail.com 0277 724 270
Jaimar - Software Development - Writing main methods code and extending code based on testing Contact details: 02108733963 ong.jay27@yahoo.co.nz