23 October 2011
Week 6 - Beta Prototype Demos
26/10/11 16:27 Filed in: 480
During the lab on Thursday this week and Tuesday next week, I’d like to see demonstrations of your team’s beta prototype. If you want to, you can put together a brief presentation and do it in front of the whole class; otherwise I’ll visit the teams and go over their demo with them.
Lab Week 7 Available: Hexagonal Wumpus World Exploration
26/10/11 16:17 Filed in: 480
Feedback on Team Work
26/10/11 16:15 Filed in: 480
Around the midpoint of the quarter, I’d like to check if all the teams are doing well in terms of collaboration and work distribution. Please go to the Team Feedback form for this.
The mid-quarter version mostly helps me to determine if there are problems with teams. We’ll do another one at the end of the quarter, and the collective feedback from that one will also affect your team score, albeit to a moderate degree (most students usually get scores around 16-18 out of 20 for this).
The mid-quarter version mostly helps me to determine if there are problems with teams. We’ll do another one at the end of the quarter, and the collective feedback from that one will also affect your team score, albeit to a moderate degree (most students usually get scores around 16-18 out of 20 for this).
Quiz Week 6 on Tue, Oct. 25
24/10/11 14:55 Filed in: 480
We will have the usual quiz on Tue this week, on the topic “Local Search and Constraint Satisfaction.” As usual, it will be available from 9:30 - 11:00 for the morning section, and 4:30 - 6:00 in the afternoon, with a 1 hour time limit.
Clarification of Milestone Due Dates and Peer Team Evaluations
24/10/11 14:29 Filed in: 480
I’ve labeled the milestones by the week when they are due, and I expect them to be completed by the end of the day on Thursday of that week. So Milestone Week 6 is due this week, on Thursday, by 23:59:59. If your team is a few days behind, you can request an extension for the milestone, which I usually grant. The extension is usually over the weekend, and needs to be requested via email.
The evaluation process involves at a minimum the review of the documentation produced by the development team. If possible, the evaluation team should download and install prototypes and try out the system, preferably on the basis of the evaluation plan put together by the development team in Milestone Week 4. At the discretion of the evaluation team, they can also meet with the development team to discuss the project, or to see the current status of the system under development. This is especially advisable if the prototype or final system requires special software or hardware not available to the development team
The evaluation is due one week after the respective milestone. However, I won’t penalize the evaluation team if the development team delivers the milestone late. So as of today (Mon, Week 6) you should have the evaluation of Milestone Week 4 completed.
The evaluation process involves at a minimum the review of the documentation produced by the development team. If possible, the evaluation team should download and install prototypes and try out the system, preferably on the basis of the evaluation plan put together by the development team in Milestone Week 4. At the discretion of the evaluation team, they can also meet with the development team to discuss the project, or to see the current status of the system under development. This is especially advisable if the prototype or final system requires special software or hardware not available to the development team
The evaluation is due one week after the respective milestone. However, I won’t penalize the evaluation team if the development team delivers the milestone late. So as of today (Mon, Week 6) you should have the evaluation of Milestone Week 4 completed.
Lab Week 6 Available
24/10/11 14:27 Filed in: 480
I just published the lab for this week. I changed the topic from “local search methods” to “Games and AI”.