> 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/project-work/mechanism-design-report.md).

# Mechanism Design Report

### Overview <a href="#overview" id="overview"></a>

This is the first project that will be a classical one usually taught nationwide, providing you with basic hands-on experience with mechanisms and transmission. Due to the limitation of the equipment, we will spend four weeks starting from Week 03 to complete a project report by each team.

Since we have four sets of the equipment, so each task force will be able to complete a report. It would also be a good chance for your team to get to know all members and make a wise decision on which task force to join later on for the second project on machine design.

### Mechanism Design Project <a href="#mechanism-design-project" id="mechanism-design-project"></a>

Instructions for conducting the Mechanism Design lab project.

[ME303-MechanismDesign-Instructions.pdf](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fliz72SG2VHq4ab4qMVYb%2Fuploads%2F2XlBWQNSNuZ28IJEaK7M%2FME303-MechanismDesign-Instructions.pdf?alt=media\&token=4b275feb-b7fe-4f5f-9299-f57dfeb0ecaf)

#### Report template for Planar Mechanisms I\&II <a href="#report-template-for-planar-mechanisms-i-and-ii" id="report-template-for-planar-mechanisms-i-and-ii"></a>

[ME303-MechanismDesign-Planar-I-II.pdf](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fliz72SG2VHq4ab4qMVYb%2Fuploads%2FmwLjUMkddfhHTRlR6zBY%2FME303-MechanismDesign-Planar-I-II.pdf?alt=media\&token=03d2c1d8-04e0-4c81-b4e2-17e5ec15ce86)

#### Report template for Planar Mechanisms III\&IV <a href="#report-template-for-planar-mechanisms-iii-and-iv" id="report-template-for-planar-mechanisms-iii-and-iv"></a>

[ME303-MechanismDesign-Planar-III-IV.pdf](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fliz72SG2VHq4ab4qMVYb%2Fuploads%2FYwLq30rdYm1XLOq61kvg%2FME303-MechanismDesign-Planar-III-IV.pdf?alt=media\&token=2fd757e3-6ec2-4d63-8c82-c106099de3e7)

### Report Submission <a href="#report-submission" id="report-submission"></a>

All reports for the first project are to be submitted after completing each week’s lab session.

* Each team and the task force must review the [lab schedule and submission deadline](https://x.ancorasir.com/me303-311/2020-autumn/weekly-teaching/syllabus#week-03-code-and-report) carefully.
* It is the [Design Engineer](https://x.ancorasir.com/me303-311/2020-autumn/teams-and-resources/team-roles#design-engineer)‘s responsibility to make the submission, but it requires [all members of the task force](https://x.ancorasir.com/me303-311/2020-autumn/teams-and-resources/task-forces) to participate in preparing the report.

### Role Allocation <a href="#role-allocation" id="role-allocation"></a>

By the end of the first project, upon submission of the first project report, [you and your team must fill out this form together](https://maindl.ancorasir.com/?page_id=766) by chossing:

* which [task force](https://x.ancorasir.com/me303-311/2020-autumn/teams-and-resources/task-forces) to join,
* who your [teammates](https://x.ancorasir.com/me303-311/2020-autumn/teams-and-resources/team-roles#student-design-team) are,
* which [specific role](https://x.ancorasir.com/me303-311/2020-autumn/teams-and-resources/team-roles#ad-hoc-task-forces) each member of the task force will be
* who will be the [team coordinators](https://x.ancorasir.com/me303-311/2020-autumn/teams-and-resources/team-roles#overview) towards the design theme
* and finally, work with the [Design Engineer](https://x.ancorasir.com/me303-311/2020-autumn/teams-and-resources/team-roles#design-engineer) of your task force and prepare for the [Design Need Report](https://x.ancorasir.com/me303-311/2020-autumn/project-work/design-need-report) to be submitted on [Week 07](https://x.ancorasir.com/me303-311/2020-autumn/weekly-teaching/syllabus#week-07-design-need-report).


---

# 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/project-work/mechanism-design-report.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.