> For the complete documentation index, see [llms.txt](https://x.ancorasir.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://x.ancorasir.com/me303-311/2020-autumn/course-overview/grading.md).

# Grading

Adapted from Source: <http://web.mit.edu/2.009/www/grading/Grading.html>

Some components of your grade are individual, some are common to your team section, and others are shared by your entire team. The [project workflow](https://x.ancorasir.com/me303-311/2020-autumn/project-work/workflow) illustrates how and when a team’s sections combine to make a team. In order to receive section and team-wide grade components, an individual must actively contribute to the milestone.

| **Categories**                    | **Deliverable**                                                                                                                | **% Course Grade** | **Assigned To …** |
| --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | ------------------ | ----------------- |
| Assignments (20%)                 | [10 Weekly Assignments](https://x.ancorasir.com/me303-311/2020-autumn/weekly-teaching/syllabus)                                | 20                 | Individual        |
| Lab Projects (20%)                | [Mechanism Design Report (I, II, III, IV)](https://x.ancorasir.com/me303-311/2020-autumn/project-work/mechanism-design-report) | 5                  | Task Force        |
|                                   | [Design Notebook](https://x.ancorasir.com/me303-311/2020-autumn/project-work/design-notebook)                                  | 10                 | Individual        |
|                                   | [Peer Review](https://x.ancorasir.com/me303-311/2020-autumn/project-work/peer-review)                                          | 5                  | Individual        |
| Final Presentation & Report (30%) | [Design Need Report](https://x.ancorasir.com/me303-311/2020-autumn/project-work/design-need-report)                            | 5                  | Task Force        |
|                                   | [Engineering Feasibility Report](https://x.ancorasir.com/me303-311/2020-autumn/project-work/engineering-feasibility-report)    | 5                  | Task Force        |
|                                   | [Fabrication & Cost Report](https://x.ancorasir.com/me303-311/2020-autumn/project-work/fabrication-and-assembly-report)        | 5                  | Task Force        |
|                                   | [Testing & Optimization Report](https://x.ancorasir.com/me303-311/2020-autumn/project-work/testing-and-optimization-report)    | 5                  | Task Force        |
|                                   | [Final Report & Presentation](https://x.ancorasir.com/me303-311/2020-autumn/project-work/final-report-and-presentation)        | 10                 | Team              |
| Final Exam (30%)                  | Final Exam                                                                                                                     | 30                 | Individual        |

Individual lab instructors assign grades to students in their task forces, upon review by the course instructor. All instructors work in close communication with each other – results after each milestone are discussed to ensure that grading is equitable between task forces within a team, and between teams.

Additionally, teams will obtain design feedback from several other course staff after each major project milestones. Also, after each milestone, this collective feedback is discussed in the lecture since the primary purpose of reviews is to help improve the projects and to facilitate a discussion of what approaches worked well and what can be improved upon.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://x.ancorasir.com/me303-311/2020-autumn/course-overview/grading.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.