Welcome to the me250-f09 course blog! This will be a forum for posting announcements, tips, and project highlights until the contest on December 10. The staff will post on this blog, and each team will post on their own blog, which will be linked to the course blog. Each team can follow the course blog (and any other team blogs) by directly viewing this site, by linking it from their own blog, or using a RSS reader such as Google Reader.
As part of the initial setup, you will:
- Establish the URL http://me250-f09-YOURTEAMNAME.blogspot.com, where 'YOURTEAMNAME' is your team name (without spaces). If your team name is long, an abbreviation is ok.
- Register all your teammates as users of your blog, where each person uses their own account or email address. This is important because each person will individually write a "reflection" on the team blog after the contest. This will be the final me250 assignment.
- Create a first post which includes a (brief) one-paragraph description of your strategy and machine concept, with a few screenshots/photos (no more than 2-3 is ok) of your current solid model and/or the sketch model you made for the DR.
- Create a second post which links to your team's schedule for the rest of the semester. This schedule can be in whatever format you like, i.e., it can be a .pdf file stored on a personal webspace, or it can be a google spreadsheet (perhaps the easiest option) connected by a link (use http://bit.ly to shorten the link). Make sure that anyone can see your schedule by clicking the link. The schedule should detail your week-by-week plans until December 10, and should be synchronized (or ahead of schedule with respect to) the remaining assignments/milestones listed on the course schedule (and in lecture on October 22). It should be specific to your team's machine, e.g., referring to the modules of your machine and any specific activities you plan (e.g., building any custom electronics, testing, etc.).
- Email the link to your blog to your GSI when complete (no later than 5PM Friday).
No comments:
Post a Comment