Add ChronoLoop model card
Browse files
README.md
ADDED
|
@@ -0,0 +1,45 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
---
|
| 2 |
+
license: apache-2.0
|
| 3 |
+
tags: [robotics, world-action-model, libero, loopwam, chronoloop]
|
| 4 |
+
---
|
| 5 |
+
# ChronoLoop checkpoints
|
| 6 |
+
|
| 7 |
+
ChronoLoop adds a small recurrent memory to LoopWAM v0: 16 memory tokens ride through the
|
| 8 |
+
pre-blocks and the shared core loops with the observation, are read out after the last core
|
| 9 |
+
loop, squashed and mixed into a carried state, and are fed back at the next replanning query.
|
| 10 |
+
Non-memory tokens read the memory through a per-head gate `tanh(alpha)` that starts at 0, so
|
| 11 |
+
every run starts exactly at its parent.
|
| 12 |
+
|
| 13 |
+
Every run fine-tunes the same parent, `anhdao69/LoopWAM_NT/libero-all-suites/v0-video4-action4`
|
| 14 |
+
(LoopWAM v0, 4 video / 4 action core loops, 388/400 on the four LIBERO suites), on all four
|
| 15 |
+
LIBERO suites (1,712 demonstrations, 277,713 windows) for 10 epochs with global batch 128
|
| 16 |
+
(32 streams x 4 consecutive windows, truncated BPTT S = 4). The schedule, noise and data order
|
| 17 |
+
are shared by all runs, so they differ only in the memory flags.
|
| 18 |
+
|
| 19 |
+
| Folder | Run | Definition |
|
| 20 |
+
|---|---|---|
|
| 21 |
+
| `CL-0_no-memory_a4` | CL-0 | No memory (control), K_a = 4 |
|
| 22 |
+
| `CL-A_mem16-learned-loopwrite_a4` | CL-A | Memory written by the shared core loops (default ChronoLoop) |
|
| 23 |
+
| `CL-REG_mem16-reset-registers_a4` | CL-REG | Same 16 tokens reset to s = 0 every query |
|
| 24 |
+
| `CL-W2_mem16-learned-external-updater_a4` | CL-W2 | Read-only memory in the backbone; separate 1-block updater |
|
| 25 |
+
| `CL-0-at1_no-memory_a1` | CL-0@1 | CL-0 with 1 action core loop |
|
| 26 |
+
| `CL-A-at1_mem16-learned-loopwrite_a1` | CL-A@1 | CL-A with 1 action core loop |
|
| 27 |
+
| `CL-FRAME_history-frame-k3_a4` | CL-FRAME | No memory; observation from query k-3 as extra gated clean frame |
|
| 28 |
+
|
| 29 |
+
Each folder has `epoch_08/`, `epoch_09/` and `epoch_10/` with `policy.pt` (weights only, format
|
| 30 |
+
`chronoloop-v1`) and `config.json`, plus the run's `manifest.json`, `metrics.jsonl` and `timing.json`.
|
| 31 |
+
A folder appears only after its training has written those epochs, and every upload is checked against
|
| 32 |
+
the local SHA-256.
|
| 33 |
+
|
| 34 |
+
Load with the `chrono` branch of LoopWAM_NT:
|
| 35 |
+
|
| 36 |
+
```python
|
| 37 |
+
from fastwam.models.wan22.chronoloop import ChronoConfig, create_chronoloop
|
| 38 |
+
import torch
|
| 39 |
+
payload = torch.load('policy.pt', map_location='cpu', weights_only=False, mmap=True)
|
| 40 |
+
model, _ = create_chronoloop(ChronoConfig(**payload['chrono']), 'Wan2.1_VAE.pth', checkpoint_path='policy.pt', device='cuda')
|
| 41 |
+
# per replanning query: out = model.chrono_infer_action(image, proprio, context, mask, state=state); state = out['state']
|
| 42 |
+
```
|
| 43 |
+
|
| 44 |
+
Rollouts: `scripts/evaluate_chronoloop_libero.py` (700 policy steps, 30 settling steps, replan every 10 actions,
|
| 45 |
+
memory reset at episode start, fixed or fresh noise).
|