Supervised Fine-Tuning in NeMo RL#
This document explains how to perform SFT within NeMo RL. It outlines key operations, including initiating SFT runs, managing experiment configurations using YAML, and integrating custom datasets that conform to the required structure and attributes.
Launch an SFT Run#
The script, examples/run_sft.py, can be used to launch an experiment. This script can be launched either locally or via Slurm. For details on how to set up Ray and launch a job using Slurm, refer to the cluster documentation.
Be sure to launch the job using uv
. The command to launch an SFT job is as follows:
uv run examples/run_sft.py --config <PATH TO YAML CONFIG> <OVERRIDES>
If not specified, config
will default to examples/configs/sft.yaml.
Example Configuration File#
NeMo RL allows users to configure experiments using yaml
config files. An example SFT configuration file can be found here.
To override a value in the config, either update the value in the yaml
file directly, or pass the override via the command line. For example:
uv run examples/run_sft.py \
cluster.gpus_per_node=1 \
logger.wandb.name="sft-dev-1-gpu"
Reminder: Don’t forget to set your HF_HOME
, WANDB_API_KEY
, and HF_DATASETS_CACHE
(if needed). You’ll need to do a huggingface-cli login
as well for Llama models.
Datasets#
SFT datasets in NeMo RL are encapsulated using classes. Each SFT data class is expected to have the following attributes:
formatted_ds
: The dictionary of formatted datasets. This dictionary should containtrain
andvalidation
splits, and each split should conform to the format described below.task_spec
: TheTaskDataSpec
for this dataset. This should specify the name you choose for this dataset.
SFT datasets are expected to follow the Hugging Face chat format. Refer to the chat dataset document for details. If your data is not in the correct format, simply write a preprocessing script to convert the data into this format. data/hf_datasets/squad.py has an example:
def format_squad(data):
return {
"messages": [
{
"role": "system",
"content": data["context"],
},
{
"role": "user",
"content": data["question"],
},
{
"role": "assistant",
"content": data["answers"]["text"][0],
},
]
}
NeMo RL SFT uses Hugging Face chat templates to format the individual examples. Three types of chat templates are supported, which can be configured via tokenizer.chat_template
in your yaml config (see sft.yaml for an example):
Apply the tokenizer’s default chat template. To use the tokenizer’s default, either omit
tokenizer.chat_template
from the config altogether, or settokenizer.chat_template="default"
.Use a “passthrough” template which simply concatenates all messages. This is desirable if the chat template has been applied to your dataset as an offline preprocessing step. In this case, you should set
tokenizer.chat_template
to None as follows:tokenizer: chat_template: NULL
Use a custom template: If you would like to use a custom template, create a string template in jinja format, and add that string to the config. For example,
tokenizer: custom_template: "{% for message in messages %}{%- if message['role'] == 'system' %}{{'Context: ' + message['content'].strip()}}{%- elif message['role'] == 'user' %}{{' Question: ' + message['content'].strip() + ' Answer: '}}{%- elif message['role'] == 'assistant' %}{{message['content'].strip()}}{%- endif %}{% endfor %}"
By default, NeMo RL has support for Squad
and OpenAssistant
datasets. Both of these datasets are downloaded from Hugging Face and preprocessed on-the-fly, so there’s no need to provide a path to any datasets on disk.
Adding a new dataset is a straightforward process.
As long as your custom dataset has the formatted_ds
and task_spec
attributes described above, it can serve as a drop-in replacement for Squad and OpenAssistant.
Evaluate the Trained Model#
Upon completion of the training process, you can refer to our evaluation guide to assess model capabilities.