fine-tuning-openvla-oft

Fine-tunes and evaluates OpenVLA-OFT robot policies with LoRA and continuous action heads.

13.0k|930|Updated Nov 3, 2025
One-click install
npx skills add https://github.com/Orchestra-Research/AI-research-SKILLs --skill fine-tuning-openvla-oft-orchestra-research
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fine-tuning-openvla-oft
Source: https://github.com/Orchestra-Research/AI-research-SKILLs/tree/main/18-multimodal/openvla-oft
Command: npx skills add https://github.com/Orchestra-Research/AI-research-SKILLs --skill fine-tuning-openvla-oft-orchestra-research

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires torch, transformers, peft, draccus, accelerate, wandb, fastapi, uvicorn, tensorflow, robosuite, and includes references (resource) components.

What problem does it solve? Reproducing OpenVLA-OFT paper results and adapting OpenVLA for robot action generation requires navigating complex environment setup, LoRA training configs, LIBERO/ALOHA evaluation pipelines, and subtle train-inference flag mismatches that silently degrade policy performance. ## Core Features & Use Cases - LIBERO Evaluation & Fine-Tuning: Run pretrained checkpoints or train LoRA-adapted policies on libero_spatial, libero_object, libero_goal, and libero_10 RLDS datasets with paper-validated hyperparameters. - ALOHA OFT+ Training & Deployment: Preprocess real-robot demonstrations, train with FiLM conditioning and 3 camera streams, then serve via a FastAPI server-client inference stack. - Config Parity & Troubleshooting: Enforce critical invariants (action head, FiLM, image count, LoRA rank, center_crop, unnorm_key) and resolve common failures like cross-GPU LoRA merge issues and libffi errors. - Use Case: A robotics researcher wants to reproduce the 97.1% average LIBERO success rate from the OpenVLA-OFT paper, then fine-tune a custom policy on their own ALOHA demonstrations and deploy it to a real robot. ## Quick Start Ask the AI to evaluate the pretrained OpenVLA-OFT checkpoint on the LIBERO-Spatial task suite with 50 trials per task.

Frequently Asked Questions about fine-tuning-openvla-oft

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fine-tune OpenVLA on LIBERO with LoRA?▼

Launch vla-scripts/finetune.py via torchrun on 8 GPUs with use_l1_regression=True, lora_rank=32, learning_rate=5e-4, and an RLDS dataset like libero_spatial_no_noops. Evaluate 50k, 100k, and 150k checkpoints and keep the best by task success rate.

What is the difference between OpenVLA-OFT and OFT+?▼

OFT disables FiLM conditioning and uses 2 camera images, targeting LIBERO simulation. OFT+ enables FiLM for stronger language grounding and uses 3 image streams, targeting ALOHA real-world bimanual tasks.

OpenVLA-OFT vs OpenPI: which VLA fine-tuning approach should I use?▼

Use OpenVLA-OFT when adapting the openvla-7b backbone with LoRA and continuous L1 or diffusion action heads on LIBERO or ALOHA. Choose OpenPI-based workflows when you need pi0 or pi0.5 model architectures instead.

Why does OpenVLA-OFT evaluation success drop after moving checkpoints to a different GPU?▼

Performance drops occur because merged adapter artifacts mismatch across hardware and runtime stacks. Re-merge the LoRA weights on the target machine with merge_lora_weights_and_save.py, then re-run evaluation with identical runtime flags.

Why is my LIBERO evaluation success rate much lower than the paper results?▼

Low success usually comes from train-eval config mismatches, most commonly missing center_crop=True when trained with image_aug=True. Also verify num_images_in_input, use_film, lora_rank, and unnorm_key parity between training and evaluation.

What GPU and VRAM are required for OpenVLA-OFT training and inference?▼

LIBERO evaluation needs about 16 GB VRAM on a single GPU, while ALOHA evaluation needs about 18 GB. Fine-tuning uses 8x A100 GPUs at roughly 27 GB per GPU for LIBERO and 35 GB per GPU for ALOHA OFT+.