You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Note: Kubernetes requires workload names to be valid DNS labels (lowercase, no underscores or periods).
79
79
export RUN_NAME=<RUN_NAME>
80
80
81
-
# Number of accelerator chips per VM.
82
-
# - TPU v5e (single host): 8
83
-
# - TPU v5p (single host): 4
84
-
# - TPU v6e (single host): 8
81
+
# Number of accelerator chips per VM. For example, use 8 for a v5p-8 VM.
85
82
export CHIPS_PER_VM=<CHIPS_PER_VM>
86
83
```
87
84
88
85
## Get your model checkpoint
89
86
87
+
This section explains how to prepare your model checkpoint for use with MaxText. It sets `MAXTEXT_CKPT_PATH`, which is passed to `load_parameters_path` in the training command below.
88
+
90
89
### Option 1: Using an existing MaxText checkpoint
91
90
92
91
If you already have a MaxText-compatible model checkpoint, simply set the
### Option 2: Converting from a Hugging Face checkpoint
100
99
101
-
Refer the steps in [Hugging Face to MaxText](hf-to-maxtext) to convert a hugging face checkpoint to MaxText. Make sure you have correct checkpoint files converted and saved. Similar to Option 1, set the following environment variable and move on to the next section.
100
+
Refer to [Hugging Face to MaxText](hf-to-maxtext) to convert a Hugging Face checkpoint to MaxText format. After conversion finishes, set `MAXTEXT_CKPT_PATH`to the converted MaxText checkpoint path.
0 commit comments