> 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-13.md).
# Week 13
[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
Dear all student designers, as we approach the end of the semester, I hope you are having a wonderful time with us through a fruitful journey of mechanical design. Be aware that the end of the this semester is only two weeks away, and I can’t wait to check out the final designs of your machine, gradually taking a physical form.
* Testing & Optimization Report
* This report provides you with a chance to revise and review your initial design, adding comments and revisions that reflect your learning experience throughout this class. It doesn’t matter if the actual design presented in this report is different from the initial design (it is actually expected so), but it is critically important for you to review the design need of your machine and the production line, check all technical specifications of the assembled machine against the earlier design, and explain how it has evolved since then.
* Please also be aware that this report is very close to the final report. It is advised that you should take a quick look at the final report template and prepare yourself for that. You can view this week’s report as a preliminary version, which you will update and revise thoroughly in your final report to present the whole design.
* Peer-Review of 2-page Design Notebook
* Here’s the [link](https://maindl.ancorasir.com/?page_id=660) to conduct the peer-review, which is due this Saturday at noon.
* We will update the 2-page design notebook on your team’s website (password protected) earlier this week.
* Please be sure to review the[Peer Review Instructions](https://x.ancorasir.com/me303-311/2020-autumn/project-work/peer-review-instructions) as we discussed when making your constructive criticism.
* Purchase and Assembly
* By this week, you should already finalized all purchase request. So keep an eye on the shipping and prepare yourself on the final assembly.
* **System Integrators**, remember to checklist all design requirement of the whole production line and communicate with all task forces.
* **Financial Officers**, please keep track of the budget spending and summarize the budget usage.
* **Tool Officers**, please keep track of the tool usage and make sure nothing is missing.
* **Information Officers**, please work with the System Integrator and start preparing the final report.
* **Team Site Masters**, please be sure to clean the lab after use and keep everything tidy.
* **Safety Officers**, be aware of the potential safety issues during the lab session and prepare for the final report.
* **Yoda Officers**, please talk with each of your team member (not just in your task force), and make sure everyone has what they need.
* **Video Log Officer**, be sure to take pictures/videos to document your team’s effort and collect material for the final presentation.
### Lecture on Monday
[View Fullscreen](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fliz72SG2VHq4ab4qMVYb%2Fuploads%2FJxmVX6ifADsSrZudYi0e%2FME303-Wk13-Mechanical-Springs.pdf?alt=media\&token=51bf15e7-68e1-436e-b2bd-30926f19848d)
[ME303-Wk13-Mechanical-Springs.pdf](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fliz72SG2VHq4ab4qMVYb%2Fuploads%2FJxmVX6ifADsSrZudYi0e%2FME303-Wk13-Mechanical-Springs.pdf?alt=media\&token=51bf15e7-68e1-436e-b2bd-30926f19848d)
### 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\] Submit Testing & Optimization Report for all students before Saturday at noon](https://x.ancorasir.com/me303-311/2020-autumn/project-work/testing-and-optimization-report)
* [\[Online\] Peer Review of 2-page Design Notebook for Week 12 before Saturday at noon](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)
---
# 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-13.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.