Cookbook Recipes - Tinker Documentation

Cookbook Recipes

Tinker allows you to flexibly customize your training environment. We will first introduce a few simple training scripts to help you get started, and then cover a broad range of different use cases.

Getting Started

Tinker Cookbook comes with useful abstractions so you can flexibly customize your experiments. Here are some minimal launch scripts:

To explain what goes under-the-hood, we also provide minimal, self-contained scripts that directly use the Tinker API to train LLMs.

More Post-Training Examples

Building on Tinker and Tinker Cookbook, we can easily customize a wide range of training environments for LLMs. We provide the following examples:

These examples are located in each subfolder, and their README.md file will walk you through the key implementation details, the commands to run them, and the expected performance.

Logging and Recovering From Training Interruptions

Our examples support the following CLI arguments to log the results.

  1. wandb_project: When provided, logs will be sent to your Weights & Biases project. Without this argument, training scripts save logs locally only.
  2. log_path: Controls where training artifacts are saved.
    • Default behavior: If not specified, each run generates a unique name and saves to /tmp/tinker-examples
    • Output files:
      • {log_path}/metrics.jsonl saves training metrics.
      • {log_path}/checkpoints.jsonl records all the checkpoints saved during training. You can share these checkpoints for model release, offline evaluation, etc.
    • Resuming: When using an existing log_path, you can either overwrite the previous run or resume training. This is particularly useful for recovering from runtime interruptions.