Policies and training#
This page summarizes policies and models for learning and development. For the initial training of AlohaMini, you can still verify the data and equipment along the ACT Main Line; other policies are configured according to their respective dependencies, input formats, and running interfaces.
1. Select the reading entrance#
policy/Topic |
Tutorial entrance |
Reading highlights |
|---|---|---|
ACT |
action chunk, training and evaluation |
|
AM-ACT |
Discrete action dimensions, fixed dimensions, loss groups, and output scaling |
|
Diffusion |
Implementation and parameter description |
|
SmolVLA |
Model dependencies, fine-tuning, inference and data |
|
Pi0 / Pi0.5 |
LeRobot’s built-in implementation is different from Standalone OpenPI |
|
Pi0 FAST |
Action representation and model use |
|
GR00T |
Modality, configuration and training |
|
RTC |
Asynchronous action blocks and compatibility policies |
|
Multitasking DiT |
Multitasking configuration and data |
|
FastWAM |
Models and exclusive dependencies |
|
MolmoAct2 |
Model input, fine-tuning and use |
|
VLA-JEPA |
Configure, train and deploy |
|
EO-1 / Evo-1 |
Corresponding implementation version and dependencies |
|
LingBot-VA / Wall-OSS / XVLA |
Data and interfaces specific to each model |
|
TD-MPC / VQ-BeT / SARM |
Part of the README is for reference, please read the corresponding text and code carefully. |
View all policy tutorials. Before using other policies, please confirm the input, action dimensions and inference interface of AlohaMini, and complete the real machine verification.
2. Before moving from ACT data to other policies#
Keep a copy of the validated dataset and ACT baseline documenting cameras, feature order, action units, and calibration.
Install the corresponding extras according to the model tutorial, and check the basic weights and usage conditions.
Confirm that the image name, language task field, state/action dimension, and normalized statistics are consistent with the model requirements.
Choose independent output directories and experiment names to avoid overwriting existing checkpoints.
First run a small-scale data loading and training check to confirm that the log, loss, and save results are normal.
Check the inference interface, control frequency, and action block policy when deploying; ACT does not use the RTC path.
The example batch size, number of training steps, and memory records depend on the specific model and training tasks and cannot be used as resource commitments for all devices.
3. Unique parameters of AM-ACT#
AM-ACT allows some action dimensions to be categorical, while the remaining dimensions are still trained as continuous values.
parameters |
function |
|---|---|
|
Dimensions that are excluded from training and fixed to zero in the normalized space |
|
Dimensional indexing using categorical predictions |
|
The physical action values corresponding to each category are in the same order as the category. |
|
Corresponding category weight |
|
Classification loss ratio |
|
Continuous dimension grouping and group weights |
|
Select a subset of input states |
|
Scale the specified output after denormalization |
The example configuration uses [14,15,16] as a discrete dimension example; whether it corresponds to the chassis should be judged based on the actual data feature sequence. Zero in normalized space also does not necessarily equal physical zero action. For complete training commands and loading methods, see AM-ACT detailed configuration.
4. Data and training tools#
[Tutorial Library] Summarizes various topics (tutorial-library.md), including other robot and simulation benchmark examples.