2026-04-30 11:00:28 +02:00
|
|
|
#!/usr/bin/env python
|
examples(annotate): switch run_hf_job to Qwen3.6-27B (dense VLM)
Swap the annotation VLM from Qwen3.6-35B-A3B (sparse MoE, ~3B active)
to Qwen3.6-27B (dense, 27B all-active). Per Scale's dense-captioning
study, model capacity is the #1 lever and the dominant failure is
visual grounding — both helped by ~9x more active params. Qwen3.6-27B
is a vision-language model (vision encoder, image + video), same family
so the chat template / video handling / enable_thinking=false flag are
unchanged, and at 27B dense it still fits one H200 per server, so the
two-parallel-server layout (TP=1, one per GPU) is preserved — no
throughput-layout change, just a much stronger model.
Kept: parallel_servers=2, num_gpus=2, max-model-len 32768 (the 32-frame
embedded budget is ~10k tokens, well under), gpu-mem 0.8.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-06-02 16:16:26 +02:00
|
|
|
"""Launch ``lerobot-annotate`` on a Hugging Face job (vllm + Qwen3.6-27B VLM).
|
2026-04-30 11:00:28 +02:00
|
|
|
|
|
|
|
|
Spawns one ``h200x2`` job that:
|
|
|
|
|
|
|
|
|
|
1. installs this branch of ``lerobot`` plus the annotation extras,
|
examples(annotate): switch run_hf_job to Qwen3.6-27B (dense VLM)
Swap the annotation VLM from Qwen3.6-35B-A3B (sparse MoE, ~3B active)
to Qwen3.6-27B (dense, 27B all-active). Per Scale's dense-captioning
study, model capacity is the #1 lever and the dominant failure is
visual grounding — both helped by ~9x more active params. Qwen3.6-27B
is a vision-language model (vision encoder, image + video), same family
so the chat template / video handling / enable_thinking=false flag are
unchanged, and at 27B dense it still fits one H200 per server, so the
two-parallel-server layout (TP=1, one per GPU) is preserved — no
throughput-layout change, just a much stronger model.
Kept: parallel_servers=2, num_gpus=2, max-model-len 32768 (the 32-frame
embedded budget is ~10k tokens, well under), gpu-mem 0.8.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-06-02 16:16:26 +02:00
|
|
|
2. boots two vllm servers (one per GPU) with Qwen3.6-27B (dense VLM),
|
2026-05-26 04:42:10 +00:00
|
|
|
3. runs the plan / interjections / vqa modules across the dataset
|
2026-06-02 11:48:05 +02:00
|
|
|
in free-form mode (each episode generates its own subtasks +
|
|
|
|
|
memory),
|
2026-05-26 04:42:10 +00:00
|
|
|
4. uploads the annotated dataset to ``--dest_repo_id`` (when set)
|
2026-05-22 11:43:06 +00:00
|
|
|
or back to ``--repo_id``.
|
2026-04-30 11:00:28 +02:00
|
|
|
|
|
|
|
|
Usage:
|
|
|
|
|
|
2026-05-18 12:03:25 +02:00
|
|
|
HF_TOKEN=hf_... uv run python examples/annotations/run_hf_job.py
|
2026-04-30 11:00:28 +02:00
|
|
|
|
2026-05-22 11:43:06 +00:00
|
|
|
Adjust ``CMD`` below to point at your own dataset / target hub repo.
|
2026-04-30 11:00:28 +02:00
|
|
|
"""
|
|
|
|
|
|
|
|
|
|
import os
|
|
|
|
|
|
|
|
|
|
from huggingface_hub import get_token, run_job
|
|
|
|
|
|
|
|
|
|
token = os.environ.get("HF_TOKEN") or get_token()
|
|
|
|
|
if not token:
|
2026-05-08 12:18:09 +02:00
|
|
|
raise RuntimeError("No HF token. Run `huggingface-cli login` or `export HF_TOKEN=hf_...`")
|
2026-04-30 11:00:28 +02:00
|
|
|
|
|
|
|
|
CMD = (
|
|
|
|
|
"apt-get update -qq && apt-get install -y -qq git ffmpeg && "
|
|
|
|
|
"pip install --no-deps "
|
|
|
|
|
"'lerobot @ git+https://github.com/huggingface/lerobot.git@feat/language-annotation-pipeline' && "
|
|
|
|
|
"pip install --upgrade-strategy only-if-needed "
|
2026-05-22 11:43:06 +00:00
|
|
|
"datasets pyarrow av jsonlines draccus gymnasium torchcodec mergedeep pyyaml-include toml typing-inspect "
|
|
|
|
|
"openai && "
|
2026-04-30 11:00:28 +02:00
|
|
|
"export VLLM_MEMORY_PROFILER_ESTIMATE_CUDAGRAPHS=0 && "
|
|
|
|
|
"export VLLM_VIDEO_BACKEND=pyav && "
|
|
|
|
|
"lerobot-annotate "
|
2026-06-02 12:08:15 +02:00
|
|
|
"--repo_id=pepijn223/robocasa_smoke_2atomic_v3 "
|
|
|
|
|
"--dest_repo_id=pepijn223/robocasa_smoke_2atomic_v3_ann "
|
2026-05-18 12:03:25 +02:00
|
|
|
"--push_to_hub=true "
|
2026-04-30 11:00:28 +02:00
|
|
|
"--vlm.backend=openai "
|
examples(annotate): switch run_hf_job to Qwen3.6-27B (dense VLM)
Swap the annotation VLM from Qwen3.6-35B-A3B (sparse MoE, ~3B active)
to Qwen3.6-27B (dense, 27B all-active). Per Scale's dense-captioning
study, model capacity is the #1 lever and the dominant failure is
visual grounding — both helped by ~9x more active params. Qwen3.6-27B
is a vision-language model (vision encoder, image + video), same family
so the chat template / video handling / enable_thinking=false flag are
unchanged, and at 27B dense it still fits one H200 per server, so the
two-parallel-server layout (TP=1, one per GPU) is preserved — no
throughput-layout change, just a much stronger model.
Kept: parallel_servers=2, num_gpus=2, max-model-len 32768 (the 32-frame
embedded budget is ~10k tokens, well under), gpu-mem 0.8.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-06-02 16:16:26 +02:00
|
|
|
"--vlm.model_id=Qwen/Qwen3.6-27B "
|
2026-04-30 11:00:28 +02:00
|
|
|
"--vlm.parallel_servers=2 "
|
|
|
|
|
"--vlm.num_gpus=2 "
|
examples(annotate): switch run_hf_job to Qwen3.6-27B (dense VLM)
Swap the annotation VLM from Qwen3.6-35B-A3B (sparse MoE, ~3B active)
to Qwen3.6-27B (dense, 27B all-active). Per Scale's dense-captioning
study, model capacity is the #1 lever and the dominant failure is
visual grounding — both helped by ~9x more active params. Qwen3.6-27B
is a vision-language model (vision encoder, image + video), same family
so the chat template / video handling / enable_thinking=false flag are
unchanged, and at 27B dense it still fits one H200 per server, so the
two-parallel-server layout (TP=1, one per GPU) is preserved — no
throughput-layout change, just a much stronger model.
Kept: parallel_servers=2, num_gpus=2, max-model-len 32768 (the 32-frame
embedded budget is ~10k tokens, well under), gpu-mem 0.8.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-06-02 16:16:26 +02:00
|
|
|
'--vlm.serve_command="vllm serve Qwen/Qwen3.6-27B '
|
2026-04-30 11:00:28 +02:00
|
|
|
"--tensor-parallel-size 1 --max-model-len 32768 "
|
|
|
|
|
'--gpu-memory-utilization 0.8 --uvicorn-log-level warning --port {port}" '
|
|
|
|
|
"--vlm.serve_ready_timeout_s=1800 "
|
2026-05-22 11:43:06 +00:00
|
|
|
"--vlm.client_concurrency=128 "
|
2026-04-30 11:00:28 +02:00
|
|
|
"--vlm.max_new_tokens=512 "
|
2026-05-22 11:43:06 +00:00
|
|
|
"--vlm.temperature=0.7 "
|
|
|
|
|
"--executor.episode_parallelism=16 "
|
|
|
|
|
"--vlm.chat_template_kwargs='{\"enable_thinking\": false}' "
|
2026-06-02 12:08:15 +02:00
|
|
|
"--vlm.camera_key=observation.images.robot0_agentview_right "
|
fix(annotate): stop action records + augmentation from corrupting RoboCasa labels
Three compounding bugs made RoboCasa annotation produce off-task
subtasks ('move stove to stove with left arm') and drifting
augmentations ('wander around the kitchen' for 'Navigate to the stove').
1. action_records.replace_subtask_text now defaults False.
Overwriting the VLM's subtask text with a reconstruction of
hallucinated {verb,object,arm,grasp,dest} fields is high-risk:
navigation / non-manipulation tasks don't fit the schema and render
to nonsense. Records are now additive by default (emit_record_row),
never silently replacing subtask text. Flip replace_subtask_text on
only for manipulation datasets verified to render cleanly.
2. _render_action_record_to_subtask_text drops a degenerate
destination that just echoes the object (verb=move object=stove
destination=stove -> 'move stove' instead of 'move stove to stove').
Also routes 'navigate' through the 'to <dest>' preposition family.
3. module_1_task_aug_axes.txt hardened: variants MUST preserve the
goal/destination. Explicitly forbids 'Navigate to the stove' ->
'wander around the kitchen'. Only wording / arm / orientation /
grasp may vary; verb meaning, object, and destination are fixed.
examples/annotations/run_hf_job.py — corrected for RoboCasa:
* derive_task_from_video=off (was =always). The dataset task string
is authoritative and is what eval conditions on; =always threw it
away, re-derived a hallucinated task from the video, and poisoned
every downstream subtask/plan row. THIS was the dominant cause.
* n_task_rephrasings=0 + task_aug_axes left off — RoboCasa eval uses
exact task strings, so augmentation is unused/harmful.
* action_records left off — manipulation schema doesn't fit atomic /
navigation tasks.
* plan_max_steps=6 to keep atomic-task decomposition tight.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-06-02 14:34:48 +02:00
|
|
|
# Phase 1 — plan module (subtasks + plan + memory).
|
2026-06-02 15:08:25 +02:00
|
|
|
# Embed decoded frames directly (use_video_url=false) rather than
|
|
|
|
|
# handing the server a file:// clip. The embedded path is more
|
|
|
|
|
# reliable: if clip extraction ever fails, the video_url path would
|
|
|
|
|
# silently send NO video and the VLM would hallucinate subtasks from
|
annotate: cap embedded-frame budget to fit VLM context (fix 32k overflow)
Switching the plan module to embedded frames (use_video_url=false)
exposed a context overflow: at frames_per_second=2.0 with the old
max_video_frames=128 default, a 480x640 episode embeds ~128 frames ≈
33-39k vision tokens, over the model's 32768 context — every plan call
died with 'Input length exceeds maximum context length' (HTTP 400),
crashing the whole annotation job.
The video_url path never hit this because the server downsampled; the
embedded path sends every sampled frame, so the frame count is a hard
token budget.
Fix:
* config default max_video_frames 128 -> 32 (~8-10k vision tokens,
comfortable headroom for the prompt + describe/verify passes).
Frames are still sampled UNIFORMLY across the whole episode, so
longer episodes are subsampled, not truncated — full temporal
coverage preserved, just coarser density.
* run_hf_job.py: frames_per_second 2.0 -> 1.0, explicit
--plan.max_video_frames=32, with a comment explaining the token
budget and the 'do not raise toward 128 with embedded frames' rule.
Only the plan module embeds the full episode; VQA (1 frame/tick) and
interjections (4-frame window) were never at risk.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-06-02 16:02:25 +02:00
|
|
|
# the task text alone.
|
|
|
|
|
#
|
|
|
|
|
# CONTEXT BUDGET: with embedded frames, each frame is ~250-320 vision
|
|
|
|
|
# tokens. The model's context is 32768 (see --max-model-len). 32
|
|
|
|
|
# frames sampled uniformly across the episode (~8-10k tokens) fits
|
|
|
|
|
# comfortably alongside the prompt and the describe/verify passes.
|
|
|
|
|
# Do NOT raise max_video_frames toward 128 with embedded frames — that
|
|
|
|
|
# is ~33-39k tokens and overflows the context (BadRequestError 400,
|
|
|
|
|
# "Input length exceeds maximum context length").
|
2026-06-02 15:08:25 +02:00
|
|
|
"--plan.use_video_url=false "
|
annotate: cap embedded-frame budget to fit VLM context (fix 32k overflow)
Switching the plan module to embedded frames (use_video_url=false)
exposed a context overflow: at frames_per_second=2.0 with the old
max_video_frames=128 default, a 480x640 episode embeds ~128 frames ≈
33-39k vision tokens, over the model's 32768 context — every plan call
died with 'Input length exceeds maximum context length' (HTTP 400),
crashing the whole annotation job.
The video_url path never hit this because the server downsampled; the
embedded path sends every sampled frame, so the frame count is a hard
token budget.
Fix:
* config default max_video_frames 128 -> 32 (~8-10k vision tokens,
comfortable headroom for the prompt + describe/verify passes).
Frames are still sampled UNIFORMLY across the whole episode, so
longer episodes are subsampled, not truncated — full temporal
coverage preserved, just coarser density.
* run_hf_job.py: frames_per_second 2.0 -> 1.0, explicit
--plan.max_video_frames=32, with a comment explaining the token
budget and the 'do not raise toward 128 with embedded frames' rule.
Only the plan module embeds the full episode; VQA (1 frame/tick) and
interjections (4-frame window) were never at risk.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-06-02 16:02:25 +02:00
|
|
|
"--plan.frames_per_second=1.0 "
|
|
|
|
|
"--plan.max_video_frames=32 "
|
2026-06-02 16:26:14 +02:00
|
|
|
# Constant 1 fps density via windowing: episodes longer than 32s are
|
|
|
|
|
# split into 32-second windows (each 32 frames @ 1 fps, fits context),
|
|
|
|
|
# so long episodes get MORE subtasks instead of a sparser whole-episode
|
|
|
|
|
# view. describe->segment->verify runs per window; spans are merged +
|
|
|
|
|
# stitched to a contiguous whole-episode cover. 0 disables.
|
|
|
|
|
"--plan.subtask_window_seconds=32 "
|
fix(annotate): stop action records + augmentation from corrupting RoboCasa labels
Three compounding bugs made RoboCasa annotation produce off-task
subtasks ('move stove to stove with left arm') and drifting
augmentations ('wander around the kitchen' for 'Navigate to the stove').
1. action_records.replace_subtask_text now defaults False.
Overwriting the VLM's subtask text with a reconstruction of
hallucinated {verb,object,arm,grasp,dest} fields is high-risk:
navigation / non-manipulation tasks don't fit the schema and render
to nonsense. Records are now additive by default (emit_record_row),
never silently replacing subtask text. Flip replace_subtask_text on
only for manipulation datasets verified to render cleanly.
2. _render_action_record_to_subtask_text drops a degenerate
destination that just echoes the object (verb=move object=stove
destination=stove -> 'move stove' instead of 'move stove to stove').
Also routes 'navigate' through the 'to <dest>' preposition family.
3. module_1_task_aug_axes.txt hardened: variants MUST preserve the
goal/destination. Explicitly forbids 'Navigate to the stove' ->
'wander around the kitchen'. Only wording / arm / orientation /
grasp may vary; verb meaning, object, and destination are fixed.
examples/annotations/run_hf_job.py — corrected for RoboCasa:
* derive_task_from_video=off (was =always). The dataset task string
is authoritative and is what eval conditions on; =always threw it
away, re-derived a hallucinated task from the video, and poisoned
every downstream subtask/plan row. THIS was the dominant cause.
* n_task_rephrasings=0 + task_aug_axes left off — RoboCasa eval uses
exact task strings, so augmentation is unused/harmful.
* action_records left off — manipulation schema doesn't fit atomic /
navigation tasks.
* plan_max_steps=6 to keep atomic-task decomposition tight.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-06-02 14:34:48 +02:00
|
|
|
# IMPORTANT for RoboCasa: the dataset's task string ("Navigate to the
|
|
|
|
|
# stove", "Pick the mug...") is authoritative and is what eval uses.
|
|
|
|
|
# ``derive_task_from_video=off`` keeps that canonical task driving
|
|
|
|
|
# subtask generation. Do NOT use ``always`` here — it throws the real
|
|
|
|
|
# task away, asks the VLM "what is this video about?" with no hint,
|
|
|
|
|
# and the hallucinated task then poisons every subtask + plan row.
|
|
|
|
|
"--plan.derive_task_from_video=off "
|
|
|
|
|
# NO task augmentation for RoboCasa: eval conditions on the exact task
|
|
|
|
|
# strings, so synthetic rephrasings are unused at best and (when they
|
|
|
|
|
# drift, e.g. "wander around the kitchen") harmful. 0 rephrasings +
|
|
|
|
|
# axes disabled = the policy only ever sees the canonical task.
|
|
|
|
|
"--plan.n_task_rephrasings=0 "
|
|
|
|
|
# action_records OFF: the structured {verb,object,arm,grasp,dest}
|
|
|
|
|
# schema is a manipulation schema; RoboCasa navigation / atomic tasks
|
2026-06-02 14:42:36 +02:00
|
|
|
# don't fit it and the VLM hallucinates. When on, records are purely
|
|
|
|
|
# additive (emitted as style="action_record" rows) and never touch
|
|
|
|
|
# the subtask text — useful only for long composite manipulation
|
|
|
|
|
# tasks. Leave off for RoboCasa atomic / navigation.
|
fix(annotate): stop action records + augmentation from corrupting RoboCasa labels
Three compounding bugs made RoboCasa annotation produce off-task
subtasks ('move stove to stove with left arm') and drifting
augmentations ('wander around the kitchen' for 'Navigate to the stove').
1. action_records.replace_subtask_text now defaults False.
Overwriting the VLM's subtask text with a reconstruction of
hallucinated {verb,object,arm,grasp,dest} fields is high-risk:
navigation / non-manipulation tasks don't fit the schema and render
to nonsense. Records are now additive by default (emit_record_row),
never silently replacing subtask text. Flip replace_subtask_text on
only for manipulation datasets verified to render cleanly.
2. _render_action_record_to_subtask_text drops a degenerate
destination that just echoes the object (verb=move object=stove
destination=stove -> 'move stove' instead of 'move stove to stove').
Also routes 'navigate' through the 'to <dest>' preposition family.
3. module_1_task_aug_axes.txt hardened: variants MUST preserve the
goal/destination. Explicitly forbids 'Navigate to the stove' ->
'wander around the kitchen'. Only wording / arm / orientation /
grasp may vary; verb meaning, object, and destination are fixed.
examples/annotations/run_hf_job.py — corrected for RoboCasa:
* derive_task_from_video=off (was =always). The dataset task string
is authoritative and is what eval conditions on; =always threw it
away, re-derived a hallucinated task from the video, and poisoned
every downstream subtask/plan row. THIS was the dominant cause.
* n_task_rephrasings=0 + task_aug_axes left off — RoboCasa eval uses
exact task strings, so augmentation is unused/harmful.
* action_records left off — manipulation schema doesn't fit atomic /
navigation tasks.
* plan_max_steps=6 to keep atomic-task decomposition tight.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-06-02 14:34:48 +02:00
|
|
|
# Keep subtask decomposition tight for atomic tasks:
|
|
|
|
|
"--plan.plan_max_steps=6 "
|
2026-06-02 15:13:50 +02:00
|
|
|
# NOTE: the multi-call subtask quality chain (describe -> segment ->
|
|
|
|
|
# verify, 3 VLM calls/episode) is ON BY DEFAULT now. Pass
|
|
|
|
|
# --plan.subtask_describe_first=false / --plan.subtask_verify=false to
|
|
|
|
|
# disable on datasets you've verified are easy and want fewer calls.
|
2026-05-22 11:43:06 +00:00
|
|
|
# Phase 2 — interjections + speech.
|
|
|
|
|
"--interjections.max_interjections_per_episode=6 "
|
|
|
|
|
# Phase 4 — general VQA.
|
2026-06-02 15:08:25 +02:00
|
|
|
# Ground VQA on the SAME single camera as plan/interjections
|
|
|
|
|
# (--vlm.camera_key) instead of iterating every camera. The whole
|
|
|
|
|
# pipeline then focuses on one view, e.g. observation.images.base.
|
|
|
|
|
"--vqa.restrict_to_default_camera=true "
|
2026-06-02 12:08:15 +02:00
|
|
|
"--vqa.K=1 "
|
2026-05-22 11:43:06 +00:00
|
|
|
"--vqa.vqa_emission_hz=1.0"
|
2026-04-30 11:00:28 +02:00
|
|
|
)
|
|
|
|
|
|
|
|
|
|
job = run_job(
|
|
|
|
|
image="vllm/vllm-openai:latest",
|
|
|
|
|
command=["bash", "-c", CMD],
|
|
|
|
|
flavor="h200x2",
|
|
|
|
|
secrets={"HF_TOKEN": token},
|
|
|
|
|
timeout="2h",
|
|
|
|
|
)
|
|
|
|
|
print(f"Job URL: {job.url}")
|
|
|
|
|
print(f"Job ID: {job.id}")
|