Skip to content
Attune
All pages

Vector · Reference

Key numbers

Every number the competition runs on, read from its contract, and the shape of the network every entry fills.

Look-up page — built for scanning

The duel

Benchmark
robotensor/RoboTwin-Vector@vector
Tasks
16
Runs per task
10
Units per side
160 (10 × 16 tasks)
Step limit
2× the expert’s steps in the scene

Rendered from spec.json at build time — the same file the orchestrator reads.

The crown

Score margin
+3.0 pts
Most void units a duel keeps
20%

Rendered from spec.json at build time — the same file the orchestrator reads.

The submission

Architecture
vector_v1.1
Tensor manifest sha256
d652e1c440ff…

Rendered from spec.json at build time — the same file the orchestrator reads.

Filesmodel.safetensors (Git LFS), and optionally README.md and .gitattributes
Largest file8 GiB; safetensors header at most 16 MiB
Commitmentvector:<owner>/<repo>@<commit>.<digest>, at most 128 bytes
Per hotkeyOne submission

Rewards

Vector's share of miner emissions30%
Champion split, newest first40% · 30% · 20% · 10%
Of all miner emissions12% · 9% · 6% · 3%
Weights set every360 blocks, about 72 minutes

The network

Fixed by vector_v1.1; drawn on The model.

Parameters781.0 M in 753 float32 tensors, about 3.1 GB
CamerasHead, left wrist, right wrist; 320 × 240 RGB, seen at 224 × 224 after a 95% centre crop
Image encoderCLIP ViT-B/16 per camera, CLS token, width 768
Tokens per frame9: 3 cameras and 6 pose keys
History2 frames: now and the one before
Prompt1 token per 15 demonstration steps, at most 67, plus 4 sinks
Decoder6 pre-norm layers, width 768, 8 heads, MLP 3,072
Diffusion head1-D U-Net, 256 · 512 · 1024 channels, FiLM; 50-step squared-cosine schedule, 16 DDIM steps
Action chunk16 actions × 20, the first 12 executed
Action sent to the robot16 numbers: per arm position 3, quaternion 4, gripper 1

Time limits

Policy start-up
600 s
One action chunk
60 s
Policy time per unit
1,200 s
One unit
1,800 s
One duel
24 h

Rendered from spec.json at build time — the same file the orchestrator reads.

The contract

Spec version
1

Rendered from spec.json at build time — the same file the orchestrator reads.

Key numbers · Docs · Attune