> 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/deep-learning/week-9-machine-learning-strategy-1.md).

# Week 8 - Machine Learning Strategy 1 & 2

### This week you will..

* Guidelines for the projects presentations, suggestions on what to put on them, baseline and human performances.
* Talk about how to structure the training, test and validation set, and more general on how to structure the whole project.
* What about using transfer learning, end-to-end approaches, divide the problem into smaller subproblems, or using multi-tasking? Sometimes the problem can be seen from another perspective.
* Since there were no programming assignment for this week, walkthrough an LSTM tutorial on time series.

### Learning Resources

### Slides

{% embed url="<https://deeplearning.freelab.org/dl1/weeks/week9.html>" %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://opencampus.gitbook.io/opencampus-machine-learning-program/courses/archive/deep-learning/week-9-machine-learning-strategy-1.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.