> 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/project-work/me303-homework-submission-form.md).

# \[ME303] Homework Submission Form

### How to Submit your homework? <a href="#how-to-submit-your-homework" id="how-to-submit-your-homework"></a>

1. [Go to this link to download the homework for the week](https://x.ancorasir.com/me303-311/2020-autumn/project-work/deliverable).
2. (Preferably print out the homework first, then) Complete the homework.
3. Take a photo/screenshot (in high resolution) of your homework and save it in a file.
4. **RENAME THE FILE FOLLOW THE INSTRUCTIONS BELOW.**
5. Write an email in the following format to submit.

* **Email Subject Line**:
  * Zhang Sanfeng (12345678) from Team Red/Green/Blue/Yellow on Homework 01/02/…/10
* **Email To**:
  * Red Team: Mr. Zhang Baolin (<12032422@mail.sustech.edu.cn>)
  * Green Team: Mr. Yu Dongwei (<12032423@mail.sustech.edu.cn>)
  * Blue Team: Mr. Jiang Wei (<12032814@mail.sustech.edu.cn>)
  * Yellow Team: Mr. Zhang Zhen (<12032428@mail.sustech.edu.cn>)
* Attach the **renamed** file.

### HWxx-StudentID-StudentName.pdf <a href="#hwxx-studentid-studentnamepdf" id="hwxx-studentid-studentnamepdf"></a>

* You MUST rename your homework pdf BEFORE uploading, otherwise the submission will NOT be counted.
* Student **Zhang Sanfeng (12345678)** who is submitting **Homework 01** must rename the PDF as “**HW01-12345678-ZhangSanfeng.pdf**” before making the submission.
* Otherwise, Zhang Sanfeng gets ZERO points for that week’s homework, even if he submitted it in time.

### No Late Submission is allowed. <a href="#no-late-submission-is-allowed" id="no-late-submission-is-allowed"></a>

* The results & marking will be released the next Monday.


---

# 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/project-work/me303-homework-submission-form.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.