> 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/application-of-transformer-models-1/week-4-fine-tuning-pretrained-models.md).

# Week 4 - Fine-Tuning Pretrained Models

### This week you will...

* learn how to fine-tune a Hugging Face model with your own data

### Learning Resources

{% file src="/files/I2LYnpbcGU8em4Uvsl6y" %}

### Until next week you should...

* [x] complete [chapter 4](https://huggingface.co/course/chapter4/1) (Sharing Models and Tokenizers) and [chapter 5](https://huggingface.co/course/chapter5/1) (The Datasets Library) of the Hugging Face course
* [x] do a literature review on the task of you project:
  * Search for transformer models applied to similar problems
  * Focus on the structure of the input and of the output
  * Are there pretrained models that you can use?
  * Which type of model is best suited? Do you need tokenization?
  * Do you need a type of embedding layer?


---

# 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/application-of-transformer-models-1/week-4-fine-tuning-pretrained-models.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.
