> 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-09.md). # Week 09 [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 Design Need Report * Will be posted on each team’s webpage for your reference. * Friday’s class: * Friday’s class will be hosted in Room N213, New Engineering Building (consult your TA or lab instructor if you have trouble finding it). * It is up to your availability to join Friday’s class, all students are welcome. * **Each task force within Teams Yellow and Blue must send at least one delegate and bring all design notebooks within your task force for review.** * You may check out the aluminum frames or conveyor belt, or simply get familiar with the classroom as you want. * Beware of safety regulations and be careful when you enter the building, as the room is not fully prepared yet, hopefully before next Wednesday. * 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 on Power Transmission * For this week’s homework on power transmission, we will give all students two weeks to prepare it. * So the deadline for this week’s homework is NEXT Saturday at noon. * Engineering Feasibility Report * This is probably the most exciting part of this week, with all details [here](https://x.ancorasir.com/me303-311/2020-autumn/project-work/engineering-feasibility-report) (submit before this Saturday at noon). * It is totally fine if you decide to change to another design (different from the design need report), but I would generally suggest making less dramatic changes unless it is really necessary. * You are expected to provide an in-depth analysis of the feasibility of your design in this week’s report. So calculations, references, reasoning, and justifications should be a major part of your report. * Also, you are expected to prepare a series of fully prepared engineering drawings with proper dimensioning for your design, which are meant for fabrication in the next phase. * This is probably the most challenging week of this semester, and strong and tight collaboration is needed to help your team. * **Keep in mind that we want to see how you justify your design for the need of this scenario, and how to express your justification through your design.** ### Lecture on Monday [View Fullscreen](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fliz72SG2VHq4ab4qMVYb%2Fuploads%2FDfljdA6I6mX81TBTL0FV%2FME303-Wk09-Power-Transmission-Case-Study.pdf?alt=media\&token=409b40b8-d8c5-4182-b317-cc13ae6f6c60) [ME303-Wk09-Power-Transmission-Case-Study.pdf](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fliz72SG2VHq4ab4qMVYb%2Fuploads%2FDfljdA6I6mX81TBTL0FV%2FME303-Wk09-Power-Transmission-Case-Study.pdf?alt=media\&token=409b40b8-d8c5-4182-b317-cc13ae6f6c60) ### Lab/Workshop on Wednesday * 0800: Hand in your design notebook for instructor review. * 0800-0815: Ms. Zhao Dan will start this week’s class with a small activity to help your guys get to know each other better. * 0815-0950: In-class discussion within your task force and team for project preparation. ### Lab/Workshop on Friday * Friday’s class will be hosted in Room N213, New Engineering Building (consult your TA or lab instructor if you have trouble finding it). * It is up to your availability to join Friday’s class, all students are welcome. * **Each task force within Teams Yellow and Blue must send at least one delegate and bring all design notebooks within your task force for review.** * You may check out the aluminum frames or conveyor belt, or simply get familiar with the classroom as you want. * Beware of safety regulations and be careful when you enter the building, as the room is not fully prepared yet, hopefully before next Wednesday. ### Deliverables * [\[Online\] Submit Engineering Feasibility Report for all students before Saturday at noon](https://x.ancorasir.com/me303-311/2020-autumn/project-work/engineering-feasibility-report) * [\[Online\] Peer Review of 2-page Design Notebook for Week 08 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-09.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.