layout	default
title	GPT Open Source - Chapter 1: Getting Started
nav_order	1
has_children	false
parent	GPT Open Source - Deep Dive Tutorial

Chapter 1: Getting Started -- Understanding the Open-Source GPT Landscape

Welcome to Chapter 1: Getting Started -- Understanding the Open-Source GPT Landscape. In this part of GPT Open Source: Deep Dive Tutorial, you will build an intuitive mental model first, then move into concrete implementation details and practical production tradeoffs.

Introduction

The open-source GPT ecosystem represents one of the most significant movements in modern AI. Starting with OpenAI's release of the GPT-2 model weights in 2019, the community has built an impressive collection of implementations that range from educational single-file projects to production-grade training frameworks capable of handling models with hundreds of billions of parameters.

This chapter will orient you within this landscape, help you set up your development environment, and guide you through your first training run using nanoGPT -- the most accessible entry point into GPT model development.

timeline
    title Open-Source GPT Timeline
    2019 : GPT-2 weights released by OpenAI
         : minGPT created by Karpathy
    2020 : GPT-Neo project launched by EleutherAI
    2021 : GPT-J 6B released
         : GPT-NeoX framework developed
    2022 : nanoGPT released by Karpathy
         : GPT-NeoX-20B trained
    2023 : Community fine-tuning explosion
         : Cerebras-GPT released
    2024 : Continued optimization and scaling

The Open-Source GPT Family Tree

Understanding how the major open-source GPT projects relate to each other is essential before diving into code.

Educational Implementations

These projects prioritize clarity and readability over performance:

Project	Lines of Code	Key Insight	Best For
minGPT	~300 (model)	Clean OOP design, well-documented	Learning transformer architecture
nanoGPT	~300 (model)	Performance-oriented, benchmarked	Training real models, research
picoGPT	~100	Absolute minimum viable GPT	Understanding core math
x-transformers	~5000	Modular transformer components	Experimenting with variants

Research-Scale Implementations

These projects are designed for training large models:

Project	Max Scale	Training Framework	Key Feature
GPT-Neo	2.7B	Mesh TensorFlow	First open GPT-3 attempt
GPT-J	6B	JAX/Haiku	Rotary embeddings, parallel layers
GPT-NeoX	20B+	Megatron-based	3D parallelism, full pipeline
Cerebras-GPT	13B	Cerebras CS-2	Compute-optimal scaling

flowchart LR
    subgraph Educational
        A[picoGPT<br>~100 LOC] --> B[minGPT<br>~300 LOC]
        B --> C[nanoGPT<br>~300 LOC]
    end

    subgraph Research
        D[GPT-Neo<br>1.3-2.7B] --> E[GPT-J<br>6B]
        E --> F[GPT-NeoX<br>20B]
    end

    C -.->|Architecture ideas| D
    B -.->|Design patterns| C

    classDef edu fill:#e8f5e9,stroke:#2e7d32
    classDef res fill:#e3f2fd,stroke:#1565c0

    class A,B,C edu
    class D,E,F res

Setting Up Your Environment

Hardware Requirements

Setup	GPU Memory	What You Can Train	Approximate Cost
Laptop	CPU only	Character-level nanoGPT	Free
Single GPU	8-16 GB	GPT-2 124M reproduction	$0.50-1.00/hr cloud
Multi-GPU	4x 24 GB	GPT-2 774M+	$4-8/hr cloud
Cluster	8x 80 GB	GPT-J 6B scale	$20-40/hr cloud

Software Installation

# 1. Create a dedicated conda environment
conda create -n gpt-oss python=3.10 -y
conda activate gpt-oss

# 2. Install PyTorch with CUDA support
# For CUDA 11.8:
pip install torch torchvision torchaudio --index-url https://download.pytorch.org/whl/cu118
# For CUDA 12.1:
pip install torch torchvision torchaudio --index-url https://download.pytorch.org/whl/cu121

# 3. Install essential packages
pip install transformers==4.36.0
pip install datasets==2.16.0
pip install tiktoken==0.5.2
pip install wandb==0.16.1
pip install numpy==1.26.2

# 4. Verify GPU access
python -c "import torch; print(f'CUDA available: {torch.cuda.is_available()}'); print(f'GPU: {torch.cuda.get_device_name(0) if torch.cuda.is_available() else \"None\"}')"

Clone the Key Repositories

# Create a workspace
mkdir -p ~/gpt-oss-workspace && cd ~/gpt-oss-workspace

# Clone nanoGPT (primary learning tool)
git clone https://github.com/karpathy/nanoGPT.git

# Clone minGPT (reference implementation)
git clone https://github.com/karpathy/minGPT.git

# Clone GPT-NeoX (production-scale training)
git clone https://github.com/EleutherAI/gpt-neox.git

Understanding nanoGPT's Structure

nanoGPT is our primary vehicle for learning. Let us examine its structure:

nanoGPT/
├── model.py          # The GPT model definition (~300 lines)
├── train.py          # Training loop (~300 lines)
├── sample.py         # Text generation script
├── config/
│   ├── train_shakespeare_char.py   # Small character-level config
│   ├── train_gpt2.py              # GPT-2 124M reproduction config
│   └── finetune_shakespeare.py    # Fine-tuning config
├── data/
│   ├── shakespeare_char/
│   │   └── prepare.py            # Character-level data prep
│   └── openwebtext/
│       └── prepare.py            # Full GPT-2 data prep
└── bench.py          # Benchmarking script

The Core Model: `model.py`

The entire GPT model fits in roughly 300 lines. Here is the high-level structure:

import torch
import torch.nn as nn
import torch.nn.functional as F
import math
from dataclasses import dataclass

@dataclass
class GPTConfig:
    """Configuration for GPT model."""
    block_size: int = 1024       # Maximum sequence length
    vocab_size: int = 50304      # GPT-2 vocab size (padded for efficiency)
    n_layer: int = 12            # Number of transformer layers
    n_head: int = 12             # Number of attention heads
    n_embd: int = 768            # Embedding dimension
    dropout: float = 0.0         # Dropout rate
    bias: bool = True            # Use bias in linear layers and LayerNorms

class CausalSelfAttention(nn.Module):
    """Multi-head causal self-attention."""

    def __init__(self, config):
        super().__init__()
        assert config.n_embd % config.n_head == 0
        # Key, Query, Value projections combined
        self.c_attn = nn.Linear(config.n_embd, 3 * config.n_embd, bias=config.bias)
        # Output projection
        self.c_proj = nn.Linear(config.n_embd, config.n_embd, bias=config.bias)
        self.n_head = config.n_head
        self.n_embd = config.n_embd
        self.dropout = config.dropout
        # Causal mask
        self.register_buffer("bias", torch.tril(
            torch.ones(config.block_size, config.block_size)
        ).view(1, 1, config.block_size, config.block_size))

    def forward(self, x):
        B, T, C = x.size()  # batch, sequence length, embedding dim
        # Compute Q, K, V for all heads in batch
        q, k, v = self.c_attn(x).split(self.n_embd, dim=2)
        k = k.view(B, T, self.n_head, C // self.n_head).transpose(1, 2)
        q = q.view(B, T, self.n_head, C // self.n_head).transpose(1, 2)
        v = v.view(B, T, self.n_head, C // self.n_head).transpose(1, 2)

        # Attention: (B, nh, T, hs) x (B, nh, hs, T) -> (B, nh, T, T)
        att = (q @ k.transpose(-2, -1)) * (1.0 / math.sqrt(k.size(-1)))
        att = att.masked_fill(self.bias[:, :, :T, :T] == 0, float('-inf'))
        att = F.softmax(att, dim=-1)
        y = att @ v  # (B, nh, T, T) x (B, nh, T, hs) -> (B, nh, T, hs)

        y = y.transpose(1, 2).contiguous().view(B, T, C)
        y = self.c_proj(y)
        return y


class MLP(nn.Module):
    """Feed-forward network with GELU activation."""

    def __init__(self, config):
        super().__init__()
        self.c_fc = nn.Linear(config.n_embd, 4 * config.n_embd, bias=config.bias)
        self.gelu = nn.GELU()
        self.c_proj = nn.Linear(4 * config.n_embd, config.n_embd, bias=config.bias)
        self.dropout = nn.Dropout(config.dropout)

    def forward(self, x):
        x = self.c_fc(x)
        x = self.gelu(x)
        x = self.c_proj(x)
        x = self.dropout(x)
        return x


class Block(nn.Module):
    """Transformer block: LayerNorm -> Attention -> LayerNorm -> MLP."""

    def __init__(self, config):
        super().__init__()
        self.ln_1 = nn.LayerNorm(config.n_embd, bias=config.bias)
        self.attn = CausalSelfAttention(config)
        self.ln_2 = nn.LayerNorm(config.n_embd, bias=config.bias)
        self.mlp = MLP(config)

    def forward(self, x):
        x = x + self.attn(self.ln_1(x))  # Pre-norm residual
        x = x + self.mlp(self.ln_2(x))   # Pre-norm residual
        return x

flowchart TB
    subgraph Block["Transformer Block (repeated N times)"]
        direction TB
        Input[Input x] --> LN1[LayerNorm 1]
        LN1 --> ATTN[Causal Self-Attention]
        ATTN --> ADD1[Add Residual]
        Input --> ADD1
        ADD1 --> LN2[LayerNorm 2]
        LN2 --> MLP[Feed-Forward MLP]
        MLP --> ADD2[Add Residual]
        ADD1 --> ADD2
        ADD2 --> Output[Output]
    end

    classDef norm fill:#e8eaf6,stroke:#3f51b5
    classDef attn fill:#fce4ec,stroke:#c62828
    classDef ffn fill:#e8f5e9,stroke:#2e7d32
    classDef op fill:#fff8e1,stroke:#f57f17

    class LN1,LN2 norm
    class ATTN attn
    class MLP ffn
    class ADD1,ADD2 op

Your First Training Run

Step 1: Prepare the Shakespeare Dataset

cd ~/gpt-oss-workspace/nanoGPT

# This downloads and tokenizes the Shakespeare corpus
python data/shakespeare_char/prepare.py

This script does the following:

Downloads the complete works of Shakespeare (~1MB of text)
Creates a character-level vocabulary (65 unique characters)
Encodes the text into integer sequences
Splits into train (90%) and validation (10%) sets
Saves as train.bin and val.bin

Step 2: Configure the Training

# config/train_shakespeare_char.py - annotated
# This configuration trains a small character-level model

# Data
dataset = 'shakespeare_char'
batch_size = 64           # Number of sequences per batch
block_size = 256          # Context window size (characters)

# Model - a "baby GPT"
n_layer = 6               # 6 transformer layers
n_head = 6                # 6 attention heads
n_embd = 384              # 384-dimensional embeddings
dropout = 0.2             # 20% dropout for regularization

# Training
learning_rate = 1e-3      # Peak learning rate
max_iters = 5000          # Total training iterations
lr_decay_iters = 5000     # Learning rate decay schedule
min_lr = 1e-4             # Minimum learning rate
warmup_iters = 100        # Linear warmup steps

# Evaluation
eval_interval = 250       # Evaluate every 250 steps
eval_iters = 200          # Average loss over 200 batches

# System
device = 'cuda'           # Use GPU
compile = True            # Use torch.compile for speed

Step 3: Train the Model

# Start training
python train.py config/train_shakespeare_char.py

# Expected output:
# step 0: train loss 4.1743, val loss 4.1755
# step 250: train loss 1.8234, val loss 1.9876
# step 500: train loss 1.5321, val loss 1.6543
# ...
# step 5000: train loss 0.8012, val loss 1.4654

Step 4: Generate Text

# Generate Shakespeare-like text
python sample.py --out_dir=out-shakespeare-char

# Example output:
# ROMEO:
# What, ho! the county Paris shall not woo
# My daughter yet; she is too young and fair
# To be your bride...

Understanding What Just Happened

Let us trace through what the training loop actually does:

flowchart TD
    A[Load train.bin and val.bin] --> B[Create GPT Model]
    B --> C[Initialize Optimizer AdamW]
    C --> D{Training Loop}

    D --> E[Sample Random Batch]
    E --> F[Forward Pass]
    F --> G[Compute Cross-Entropy Loss]
    G --> H[Backward Pass]
    H --> I[Gradient Clipping]
    I --> J[Optimizer Step]
    J --> K{Eval Interval?}

    K -->|Yes| L[Compute Val Loss]
    L --> M{Best Val Loss?}
    M -->|Yes| N[Save Checkpoint]
    M -->|No| D
    N --> D

    K -->|No| D

    classDef data fill:#e3f2fd,stroke:#1565c0
    classDef model fill:#fce4ec,stroke:#c62828
    classDef train fill:#e8f5e9,stroke:#2e7d32
    classDef eval fill:#fff3e0,stroke:#ef6c00

    class A data
    class B,C model
    class E,F,G,H,I,J train
    class K,L,M,N eval

Key Metrics to Watch

Metric	Healthy Range	Warning Signs
Train Loss	Steadily decreasing	Plateaus early, spikes
Val Loss	Slightly above train loss	Diverges from train loss
Learning Rate	Follows cosine schedule	N/A (configured)
Gradient Norm	Stable, < 1.0 after clipping	Spikes, NaN values
Tokens/sec	GPU-dependent	Significantly below baseline

Comparing minGPT and nanoGPT

Both are by Andrej Karpathy, but they serve different purposes:

# minGPT style: Object-oriented, modular
from mingpt.model import GPT

model_config = GPT.get_default_config()
model_config.model_type = 'gpt2'
model_config.vocab_size = 50257
model_config.block_size = 1024
model = GPT(model_config)

# nanoGPT style: Flat, optimized, benchmarked
from model import GPTConfig, GPT

config = GPTConfig(
    block_size=1024,
    vocab_size=50304,  # Padded to nearest multiple of 64
    n_layer=12,
    n_head=12,
    n_embd=768,
)
model = GPT(config)

Aspect	minGPT	nanoGPT
Design philosophy	Clean, educational	Practical, optimized
Code organization	Multiple files, classes	Minimal files
Performance	Baseline	~2x faster with compile
GPT-2 reproduction	Not benchmarked	Verified reproduction
Vocab size	50257 (raw)	50304 (padded for GPU)
Weight initialization	Standard	Scaled residual init

Summary

In this chapter, you have:

Surveyed the open-source GPT ecosystem from educational tools to production frameworks
Set up a complete development environment for GPT experimentation
Trained your first character-level GPT model using nanoGPT
Understood the core structure of a GPT implementation
Compared minGPT and nanoGPT design philosophies

Key Takeaways

The open-source GPT ecosystem is layered: Start with nanoGPT for learning, scale to GPT-NeoX for production.
A GPT model is surprisingly simple: The core architecture is roughly 300 lines of PyTorch.
nanoGPT is the best starting point: It balances readability with real performance.
Character-level models train fast: You can see results in minutes, making them ideal for experimentation.
Understanding the training loop is fundamental: Every GPT training system follows the same basic pattern.

Next Steps

In Chapter 2: Transformer Architecture, we will dissect every component of the transformer architecture in detail -- from the mathematics of self-attention to the role of layer normalization and residual connections.

Built with insights from open-source GPT implementations.

What Problem Does This Solve?

Most teams struggle here because the hard part is not writing more code, but deciding clear boundaries for config, self, n_embd so behavior stays predictable as complexity grows.

In practical terms, this chapter helps you avoid three common failures:

coupling core logic too tightly to one implementation path
missing the handoff boundaries between setup, execution, and validation
shipping changes without clear rollback or observability strategy

After working through this chapter, you should be able to reason about Chapter 1: Getting Started -- Understanding the Open-Source GPT Landscape as an operating subsystem inside GPT Open Source: Deep Dive Tutorial, with explicit contracts for inputs, state transitions, and outputs.

Use the implementation notes around bias, torch, n_head as your checklist when adapting these patterns to your own repository.

How it Works Under the Hood

Under the hood, Chapter 1: Getting Started -- Understanding the Open-Source GPT Landscape usually follows a repeatable control path:

Context bootstrap: initialize runtime config and prerequisites for config.
Input normalization: shape incoming data so self receives stable contracts.
Core execution: run the main logic branch and propagate intermediate state through n_embd.
Policy and safety checks: enforce limits, auth scopes, and failure boundaries.
Output composition: return canonical result payloads for downstream consumers.
Operational telemetry: emit logs/metrics needed for debugging and performance tuning.

When debugging, walk this sequence in order and confirm each stage has explicit success/failure conditions.

Source Walkthrough

Use the following upstream sources to verify implementation details while reading this chapter:

nanoGPT Why it matters: authoritative reference on nanoGPT (github.com).
minGPT Why it matters: authoritative reference on minGPT (github.com).
GPT-NeoX Why it matters: authoritative reference on GPT-NeoX (github.com).
GPT-Neo Why it matters: authoritative reference on GPT-Neo (github.com).
GPT-J Why it matters: authoritative reference on GPT-J (github.com).
Chapter 1: Getting Started Why it matters: authoritative reference on Chapter 1: Getting Started (01-getting-started.md).

Suggested trace strategy:

search upstream code for config and self to map concrete implementation paths
compare docs claims against actual runtime/config code before reusing patterns in production

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Chapter 1: Getting Started -- Understanding the Open-Source GPT Landscape

Introduction

The Open-Source GPT Family Tree

Educational Implementations

Research-Scale Implementations

Setting Up Your Environment

Hardware Requirements

Software Installation

Clone the Key Repositories

Understanding nanoGPT's Structure

The Core Model: `model.py`

Your First Training Run

Step 1: Prepare the Shakespeare Dataset

Step 2: Configure the Training

Step 3: Train the Model

Step 4: Generate Text

Understanding What Just Happened

Key Metrics to Watch

Comparing minGPT and nanoGPT

Summary

Key Takeaways

Next Steps

What Problem Does This Solve?

How it Works Under the Hood

Source Walkthrough

Chapter Connections

FilesExpand file tree

01-getting-started.md

Latest commit

History

01-getting-started.md

File metadata and controls

Chapter 1: Getting Started -- Understanding the Open-Source GPT Landscape

Introduction

The Open-Source GPT Family Tree

Educational Implementations

Research-Scale Implementations

Setting Up Your Environment

Hardware Requirements

Software Installation

Clone the Key Repositories

Understanding nanoGPT's Structure

The Core Model: model.py

Your First Training Run

Step 1: Prepare the Shakespeare Dataset

Step 2: Configure the Training

Step 3: Train the Model

Step 4: Generate Text

Understanding What Just Happened

Key Metrics to Watch

Comparing minGPT and nanoGPT

Summary

Key Takeaways

Next Steps

What Problem Does This Solve?

How it Works Under the Hood

Source Walkthrough

Chapter Connections

The Core Model: `model.py`