> For the complete documentation index, see [llms.txt](https://opencampus.gitbook.io/opencampus-machine-learning-program/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://opencampus.gitbook.io/opencampus-machine-learning-program/courses/archive/week-10-special-issues-considering-your-final-projects.md).

# TensorFlow Course: Week 10 - Special Issues Considering Your Final Projects

### This week you will...

* get some additional ideas on models or areas of machine learning that were not covered in this course.
* get a quick overview of possible next steps in your machine learning journey and how to stay updated with the fast moving development in this field.

### Learning Resources

### Until next week you should...

* focus fully on your project again and prepare the project presentation for next week.
* consider the following requirements for the final presentation shown[ here](/opencampus-machine-learning-program/courses/archive/machine-learning-with-tensorflow/week-11-presentation-of-the-final-projects.md).

{% content-ref url="/pages/-MIOIx\_PyIww00jN-kJN" %}
[How to Start, Complete, and Submit Your Project](/opencampus-machine-learning-program/course-projects/requirements.md)
{% endcontent-ref %}


---

# 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://opencampus.gitbook.io/opencampus-machine-learning-program/courses/archive/week-10-special-issues-considering-your-final-projects.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.