> 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/weekly-teaching/week-07.md).

# Week 07

[Syllabus](https://x.ancorasir.com/me303-311/2020-autumn/weekly-teaching/syllabus)

[Calendar](https://maindl.ancorasir.com/?page_id=65)

[Team](https://x.ancorasir.com/me303-311/2020-autumn/teams-and-resources/student-teams)

[Project](https://x.ancorasir.com/me303-311/2020-autumn/project-work/theme)

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

This week is the deadline for the first Machine Design Report, based on this report from each task force, we will be working together towards a set of machines towards the wasteless production line. Although we planned to move all students into the New Engineering Building during this week’s class, we are still waiting for the final approval from the University President. In the meanwhile, our team of teaching staff is working very hard to refurbish the new classroom with machines, tools, and equipment for your learning experience. Nevertheless, look forward to your design need report and can’t wait to see your exciting designs and teamwork.

Be sure to review [Instructions for Peer Review](https://x.ancorasir.com/me303-311/2020-autumn/project-work/peer-review-instructions) with more details, following steps below:

* Go to your team’s webpage (password protected)
* Scroll down to the 10. Peer Review section
* Open the [Peer Review Submission](https://x.ancorasir.com/me303-311/2020-autumn/project-work/peer-review) page in a new tab
* Click through the submitted 2-page design notebooks and share your review, 1 task force at a time
* Each student needs to submit the form 3 time to complete the review of all task forces within your team
* Don’t forget to evaluate yourself
* If no student role is allocated, or no link provided for that student, type 0 for the marking

### Lecture on Monday <a href="#lecture-on-monday" id="lecture-on-monday"></a>

[View Fullscreen](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fliz72SG2VHq4ab4qMVYb%2Fuploads%2FyOVAzyjkwQesEtLKEqL7%2FME303-Wk07-Spur-Helical-Bevel-Worm-Gears.pdf?alt=media\&token=80bf8b78-9217-4e8f-8585-a899922c1a38)

[ME303-Wk07-Spur-Helical-Bevel-Worm-Gears.pdf](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fliz72SG2VHq4ab4qMVYb%2Fuploads%2FyOVAzyjkwQesEtLKEqL7%2FME303-Wk07-Spur-Helical-Bevel-Worm-Gears.pdf?alt=media\&token=80bf8b78-9217-4e8f-8585-a899922c1a38)

### Lab on Wednesday / Friday <a href="#lab-on-wednesday-friday" id="lab-on-wednesday-friday"></a>

* As recommended by Guo Weijie, each team can take 10\~15 mins to share your Design Need Report using [Feishu Doc Presentation Mode](https://www.feishu.cn/hc/en-US/articles/360033237934-Docs-Use-presentation-mode-in-Docs) and receive on-site feedback from the lab instructor (NO NEED TO PREPARE A SEPARATE POWERPOINT).
* Hand-in your design notebook for signature and review by the lab instructor
* Discuss with all members in your task force and team to work on the machine design report

### Workshop on Wednesday / Friday <a href="#workshop-on-wednesday-friday" id="workshop-on-wednesday-friday"></a>

* As recommended by Guo Weijie, each team can take 10\~15 mins to share your Design Need Report using [Feishu Doc Presentation Mode](https://www.feishu.cn/hc/en-US/articles/360033237934-Docs-Use-presentation-mode-in-Docs) and receive on-site feedback from the workshop instructor (NO NEED TO PREPARE A SEPARATE POWERPOINT).
* Hand-in your design notebook for signature and review by the lab instructor
* Discuss with all members in your task force and team to work on the machine design report

### Deliverables <a href="#deliverables" id="deliverables"></a>

* [\[Online\] Submit Design Need Report for all students](https://x.ancorasir.com/me303-311/2020-autumn/project-work/mechanism-design-report)
* [\[Online\] Peer Review of 2-page Design Notebook for Week 06](https://x.ancorasir.com/me303-311/2020-autumn/project-work/peer-review)
* [\[On-site\] Design Notebook physical review by Instructors](https://x.ancorasir.com/me303-311/2020-autumn/project-work/design-notebook)
* [\[Saturday noon\] Submit Homework06](https://x.ancorasir.com/me303-311/2020-autumn/project-work/deliverable#weekly-homework-by-individuals)


---

# 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/weekly-teaching/week-07.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.