Q: Is there enough room in the project schedule for field trips or visits from experts?
A: Yes - there is enough slack.
Q:(for both schedule teams) Does the schedule assume that 1/2 time is spent on project and robot?
A: Yes
Noted that if they change the robot schedule, then the design must be locked down by 9/14. Need to add this note to the schedule. They also clarified that the schedule assumes the same approach as last year: solve all the missions, then combine/cut.
Andrew suggested each person do a mini-project that they can have fun with and present to the group. The team agreed to table that idea and consider it when they find out the actual challenge to see if they think it will work.
A schedule gap was identified and Alex volunteered to schedule the miscellaneous jobs that don't fit under project and robot headings: technical presentation, putting together other presentation material, etc.
Michael and Andrew brought in a prototype robot design that they propose for this season. We had a short design review but agreed to hold off deciding whether or not to change the design until they understand the challenge. They would also need to test the perceived advantages of the new robot to verify that it delivers. Below are the results, but I'd like to congratulate Michael and Andrew on their initiative and the group in general for their thoughtful consideration of the impact of both changing and keeping the old design.
Pros:
- shorter - more maneuverable and can have larger implements in base
- easier to charge
- flatter wheels for more traction and less bounce
- rear sliders are the same width as marks in base to make it easier to align.
- light sensor is now behind the front wheels (affects line follower algorithm)
- implements and/or attachments need to be re-designed
- arm motor was too tight to attach the arm (already fixed)
- it might be too slow with the smaller wheels
- re-designing and testing will take schedule time
No comments:
Post a Comment