ME 333 final projects

From Mech
Revision as of 09:46, 4 March 2008 by Lynch (talk | contribs)
Jump to navigationJump to search

ME 333 final web page guidelines

Final wiki pages due at 8:00 AM Friday March 21 (finals week).

Following the templates below, substitute your project title and edit the page created when you click on it. Make sure that the pages you create have a brief but descriptive title. Ideally, your entire project should be put on a single wiki page (unless you are documenting a useful new capability; see below), along with links to any pdf files, images, code, movies, text files, or whatever helps explain your project. Be reasonable; don't upload giant files. Generally, you should keep the total amount of uploaded material to less than 10 MB, usually much less.

Page content. Your wiki page should have at least one picture of the entire system, showing clearly what it is. Generally, your wiki page should start out with this picture, names of the team members, a picture of the team (you can use the picture taken during lab 3 of your lab group, if you wish), and an overview of what your project is and how it works. Then you should have subsections: mechanical design, electrical design, code, and results and reflections. The overriding goal is to give enough detail to allow someone else to duplicate your project without excessive effort. The mechanical and electrical design sections should have lists of parts used (including part numbers, vendors, and cost, when available). The mechanical design section should have clear drawings, or sufficiently clear pictures. Circuit schematics should be given for all non-obvious circuits. The results and reflections section should give an honest assessment of how well your project turned out, and what you would do differently if you could do it again. The goal is to be as useful as possible for future student groups.

Images. In most cases, the images as viewed in the wiki page should be relatively small -- big enough that the image is useful, but not so big that the page is huge or the flow of the wiki page is disrupted. When the user clicks on the image, they can see the larger image for more detail.

Code. Your code should be modular (each function should be relatively short and perform a clearly defined function) and well commented (so others can understand it).

New capabilities for the wiki. If you have mastered a new capability not already present on the wiki that others would also find useful (e.g., you interfaced to a new kind of sensor, or developed novel communication capabilities, etc.), you should write these as separate compact wiki pages that helps a novice use the capability. You can link these pages to your project description, and we will link to them from the main hierarchy. Also, if you see any mistakes on the wiki or think some pages can be improved, you are welcome to update them. All edits are recorded by the author's name.


2008 ME 333 Final Projects

Project Title 1

Pctopic.jpg

Here are a few words describing your project, just a teaser to go with the picture at right that should give a good idea of the project.


Project Title 2

Pictopic.jpg

Here are a few words describing your project, just a teaser to go with the picture at the side.