AlexWortega commited on
Commit
2e262f4
·
verified ·
1 Parent(s): 6bad938

ablation.md: add pre-LIBERO checkpoint comparison (stage2/stage3/pretrain_A, all 0% on LIBERO closed-loop)

Browse files
Files changed (1) hide show
  1. ablation.md +19 -0
ablation.md CHANGED
@@ -221,6 +221,7 @@ actually look like - should help.
221
  | pixel + proprio age | Success | 95% CI | delta | paired 95% CI | flips | McNemar p |
222
  |---|---|---|---|---|---|---|
223
  | 0.25 s | 21/150 = 14.0% | 9.3–20.5 | -70.0 | -78.0…-61.3 | +4/-109 | 0.0000*** |
 
224
 
225
  At 0.25 s, the internally-consistent version scores **14.0%** against **23.3%** for stale pixels with fresh proprioception — significantly *worse* (-9.3 points, 20 episodes lost against 6 won, McNemar p = 0.0094), not better. So the collapse is not explained by the observation being self-inconsistent — staling proprioception on top of the pixels makes things worse, not better. Holding proprioception back to make a cached vision tower's input "agree with itself" is not a viable mitigation: geometric staleness costs, and adding more of it costs more.
226
 
@@ -286,6 +287,24 @@ done: 12 cells plus two controls, 500 + 12x150 + 2x150 = 2,300 closed-loop episo
286
  are being evaluated closed-loop on the same suite, to size how much of the 85.2%
287
  full-rate number comes from the LIBERO fine-tune itself.
288
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
289
  ## Reproduction
290
 
291
  ```bash
 
221
  | pixel + proprio age | Success | 95% CI | delta | paired 95% CI | flips | McNemar p |
222
  |---|---|---|---|---|---|---|
223
  | 0.25 s | 21/150 = 14.0% | 9.3–20.5 | -70.0 | -78.0…-61.3 | +4/-109 | 0.0000*** |
224
+ | 0.5 s | 0/150 = 0.0% | 0.0–2.5 | -84.0 | -89.3…-78.0 | +0/-126 | 0.0000*** |
225
 
226
  At 0.25 s, the internally-consistent version scores **14.0%** against **23.3%** for stale pixels with fresh proprioception — significantly *worse* (-9.3 points, 20 episodes lost against 6 won, McNemar p = 0.0094), not better. So the collapse is not explained by the observation being self-inconsistent — staling proprioception on top of the pixels makes things worse, not better. Holding proprioception back to make a cached vision tower's input "agree with itself" is not a viable mitigation: geometric staleness costs, and adding more of it costs more.
227
 
 
287
  are being evaluated closed-loop on the same suite, to size how much of the 85.2%
288
  full-rate number comes from the LIBERO fine-tune itself.
289
 
290
+ ## 9. Other checkpoints in the same repo, same harness
291
+
292
+ Three checkpoints that predate the LIBERO fine-tune, evaluated closed-loop on
293
+ `libero_spatial` with the exact same conventions and no ablation (full-rate,
294
+ 100 episodes = init states 0-9). None of them were fine-tuned on LIBERO, so this
295
+ sizes how much of the 85.2% full-rate number is the fine-tune rather than the
296
+ shared pretrain.
297
+
298
+ | Checkpoint | What it is | Success | 95% CI |
299
+ |---|---|---|---|
300
+ | `checkpoints/stage2_final` | SO-100/101 + Bridge mixture, frozen backbone | 0/100 = 0.0% | 0.0-3.7 |
301
+ | `checkpoints/stage3_final` | + spatial distillation | 0/100 = 0.0% | 0.0-3.7 |
302
+ | `tinyvla2/pretrain_A` | TinyVLA-2 cross-embodiment ablation, variant A | 0/100 = 0.0% | 0.0-3.7 |
303
+
304
+ **`tinyvla2/pretrain_A` scores 0.0% on LIBERO** (0/100), consistent with stage2/stage3: none of the three pre-fine-tune checkpoints do anything useful on this suite. This is a different model from the one the rest of this document ablates — it is the *control* arm of a separate cross-embodiment ablation (variants A/B/C), not a LIBERO checkpoint. Its own model card already reports it failing cross-embodiment transfer on held-out `jaco` (endpoint error 1392 mm vs. a 128 mm zero-prediction floor, n=8) — a result from the author, not independently reproduced here since the held-out-embodiment harness this document uses is LIBERO/MetaWorld/SO-101, not the jaco eval that number came from. `conditioning`, `morph_tokens`, and `action_space` in its config are not implemented in `modeling_tinyvla.py` as of this checkpoint family's release — they were added to `configuration_tinyvla.py` here as pass-through fields so the checkpoint would load, since variant A's own documentation states it is architecturally identical to the embodiment-ID scheme already implemented (`EmbodimentEmbedding`). Whether that also holds for variants B and C is unverified.
305
+
306
+ ---
307
+
308
  ## Reproduction
309
 
310
  ```bash