> 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-11.md).
# Week 11
[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, this week is an exciting week. Not only that you will be submitting your Engineering Feasibility Report, but also we will be having the SUSTech Sports Meeting this Friday. As the university did not plan to replace this Friday’s class, we will still host Friday’s class, but it is up to your availability to join.
* Feedback on Engineering Feasibility Report
* Will be posted on each team’s webpage for your reference.
* Wednesday & Friday’s class:
* Wednesday & Friday’s class will be hosted in Room 235, New Engineering Building (consult your TA or lab instructor if you have trouble finding it).
* 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.
* We already notified students who missed the submission (40% penalty at least), and you should check the correct week number when submitting.
* 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.
* Homework released in Week 10
* The deadline for last week’s homework is this Saturday at noon (the last homework of this semester).
* Fabrication & Assembly Report
* Besides the template provides on the website, there are three things that I’d like to emphasize
* Budget Update
* In each Task Force’s report, please include a section with a detailed list of the current spending of your task force and a brief list of the total spending of your team
* Fabrication Update
* Please list a detailed Bill of Materials of your machine, and also any other fabrication that your task force has conducted so far
* You should include the original design in CAD as well as an update of the actual fabrication using images and analysis (as much as you can)
* This is required for all pieces, especially non-standard parts that require further fabrication
* Assembly Update
* Please at least include a full 3-view drawing of your overall machine in one single assembly to show the complete machine design, including the conveyor belt, the trash cans, the robot arm and the robot stand (task force C).
* Please at least include an exploded view of the specific machine that your task force is designing (only the parts that you designed)
* Please include a detailed, step-by-step, assembly instruction to build your machine from the beginning to the end.
### Lecture on Monday
[View Fullscreen](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fliz72SG2VHq4ab4qMVYb%2Fuploads%2F92X3UcOne9wgyaYTpSfD%2FME303-Wk11-Permanent-Joints-Welding-Bonding.pdf?alt=media\&token=03fc7afc-9ede-4610-90ba-98a20512c692)
[ME303-Wk11-Permanent-Joints-Welding-Bonding.pdf](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fliz72SG2VHq4ab4qMVYb%2Fuploads%2F92X3UcOne9wgyaYTpSfD%2FME303-Wk11-Permanent-Joints-Welding-Bonding.pdf?alt=media\&token=03fc7afc-9ede-4610-90ba-98a20512c692)
### 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. (Hopefully assemble something)
### Deliverables
* [\[Online\] Submit Fabrication & Assembly Report for all students before Saturday at noon](https://x.ancorasir.com/me303-311/2020-autumn/project-work/fabrication-and-assembly-report)
* [\[Online\] Peer Review of 2-page Design Notebook for Week 10 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)
* [\[Saturday noon\] Submit Homework09](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-11.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.