> 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-12.md).
# Week 12
[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
Thank you for your submission of the Fabrication & Assembly Report. While we are reviewing your reports, please be sure to finalize the fabrication and purchase request, and start the assembly of your machines.
* Feedback on Peer Review of Design Notebooks
* Will be shared with you individually through Feishu.
* Wednesday & Friday’s class:
* Wednesday & Friday’s class will be hosted in Room 235, New Engineering Building.
* Submission of Week 12’s 2-page Design Notebook
* We will post peer-review feedback as soon as possible, and please also be reminded regarding the 2-page design notebook submission.
* Be sure to refer to the recommendations and guidelines we provided before making the submission.
* Homework released in Week 11
* The deadline for last week’s homework is this Saturday at noon (the last homework of this semester).
* Preparation of the Testing & Optimization Report
* Besides the template provides on the website, there are three things that I’d like to emphasize
* This report is the one that provides you with the opportunity to revise your overall design and check if it may hold the potential to meet the design need through the engineering specifications of your machines.
### Lecture on Monday
[View Fullscreen](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fliz72SG2VHq4ab4qMVYb%2Fuploads%2Fxy3BcFqkPXVooSjIgd50%2FME303-Wk12-Brakes-Flywheels-Bearings-Lubrications.pdf?alt=media\&token=1f501ba2-d13e-4371-b199-d3c92c5f7481)
[ME303-Wk12-Brakes-Flywheels-Bearings-Lubrications.pdf](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fliz72SG2VHq4ab4qMVYb%2Fuploads%2Fxy3BcFqkPXVooSjIgd50%2FME303-Wk12-Brakes-Flywheels-Bearings-Lubrications.pdf?alt=media\&token=1f501ba2-d13e-4371-b199-d3c92c5f7481)
### Lab/Workshop on Wednesday / Friday
* Room 235 at the New Engineering Building
* 0800: Hand in your design notebook for instructor review.
* 0800-0950: In-class discussion within your task force and team for project preparation.
### Deliverables
* [\[Online\] 2-page Design Notebook submission](https://maindl.ancorasir.com/?page_id=938)
* [\[On-site\] Design Notebook physical review by Instructors](https://x.ancorasir.com/me303-311/2020-autumn/project-work/design-notebook)
* [\[Saturday noon\] Submit Homework10](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-12.md?ask=&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.