SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 2111.03205 · 2021

LILA: Language-Informed Latent Actions

arXiv · PDF · Open in the Atlas

Code that ran

3 of 3 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (0 of them constructed an object rather than computing a result; 0 honoured the contract we drafted, 0 violated it and 0 have no contract verdict; 3 failures of our instrument; 0 no recorded run), measured 2026-11-22; repository links from the Papers with Code archive attributed under CC BY-SA, no affiliation; bodies inline only under a permissive licence as GitHub detects it. Not a reproduction of the paper's results.

"Ran" means the function executed on a synthesized input and returned a value. It is not a reproduction of the paper's results. This record, dated, as JSON: /api/ran/2111.03205.json · badge: /api/ran/2111.03205.svg

Each repository's role is a label: a classifier's output recorded on the link, or, where no role is recorded, what the Papers with Code archive marked. The line under it names its basis. Neither says who wrote the code.

RepositoryRoleRan
siddk/lila canonical (classifier label)
classifier basis: classifier_2025
2 ran · 0 no recorded run
copy not recorded community
not in the paper's declared repositories
1 ran · 0 no recorded run
FunctionStatusWhere it lives
connect2robot Ran
ran; our contract draft was wrong, not the code
this paper's copy was not recorded; identical code first harvested from Stanford-ILIAD/vla
pointer only; the stored copy get_code serves, from Stanford-ILIAD/vla, is pointer only (licence: GPL-3.0) · get_code("4011df101218876f")
How it ran

The body of this sample is withheld: this paper's copy of the code was not recorded (its link names no repository or source path), so no licence was read for it. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded.

listen2robot Ran
ran; our contract draft was wrong, not the code
siddk/lila/teleoperate.py
code served (permissive licence) · get_code("07de94ecf9a2f9c5")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1) and returned dict. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.

import socket
import numpy as np

class MockConnection:
    def __init__(self, message):
        self.message = message
    
    def recv(self, bufsize):
        return self.message.encode()

# Construct a valid state message
# Format: comma-separated values with 's' marker followed by state_length (63) values
# state_length = 7 + 7 + 7 + 42 = 63
q_vals = [0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7]  # 7 values
dq_vals = [0.01, 0.02, 0.03, 0.04, 0.05, 0.06, 0.07]  # 7 values
tau_vals = [1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6]  # 7 values
J_vals = list(np.random.randn(42))  # 42 values (7x6 reshaped to 42)

state_values = q_vals + dq_vals + tau_vals + J_vals
state_message = "prefix,s," + ",".join(str(v) for v in state_values)

conn = MockConnection(state_message)

ARGS = {
    "conn": conn
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1
Imports
numpy — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type dict — a dict output has no array shape of its own; none is stated — the instrument coerces any output to an array; for a dict output the recorded ndim 0 and dtype family float describe that coercion, not the output, and are not stated
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block
pool Ran
ran; our contract draft was wrong, not the code
siddk/lila/teleoperate.py
code served (permissive licence) · get_code("7dee1a73c093841c")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1) and returned Tensor, ndim 2, dtype family float, shape (2, 4) as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.

import torch

torch.manual_seed(0)

# The function expects:
# - output: a tuple/list where output[0] is embeddings tensor of shape (batch_size, seq_len, embedding_dim)
# - attention_mask: a tensor of shape (batch_size, seq_len) with binary values

batch_size = 2
seq_len = 3
embedding_dim = 4

# Create embeddings tensor
embeddings = torch.randn(batch_size, seq_len, embedding_dim)

# Create attention_mask tensor (binary mask)
attention_mask = torch.tensor([
    [1, 1, 1],
    [1, 1, 0]
], dtype=torch.long)

# output is expected to be indexable with [0], so wrap embeddings in a tuple
output = (embeddings,)

ARGS = {
    "output": output,
    "attention_mask": attention_mask
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1
Imports
torch — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type Tensor, ndim 2, dtype family float, shape (2, 4) — shape (2, 4) as a later run recorded it
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block

Also present in other papers' code

Of 3 samples lifted from this paper's linked repositories, 3 carry a function identity and 0 do not. Of the 3 distinct functions with an identity, 2 are also present in other papers whose code we hold (2 with at least one paper dated earlier, 0 the same month, 0 later) and 1 are only here among the 52,977 papers whose code Syntology holds (as of 2026-09-26).

Only here means: among the 52,977 papers whose code Syntology holds (51,887 with lifted samples, 1,090 through their assemblies only), as of 2026-09-26, no other paper's lifted samples or current assembly bricks contain an identical function body after normalisation.

FunctionAlso present inEarliest-datedOthers named
connect2robot 1 other paper
1 dated earlier
2105.00580 (2021-05)
Learning Visually Guided Latent Actions for Assistive Teleoperation
listen2robot 1 other paper
1 dated earlier
2105.00580 (2021-05)
Learning Visually Guided Latent Actions for Assistive Teleoperation

Presence, not direction: an identical function body in two papers' repositories does not say who wrote it, which came from which, or that either paper's method rests on it. Matching is exact after normalisation, so a renamed or edited function is not matched. Dates are when papers appeared, not when code was written. Only .py files the harvester lifted are covered; notebooks are not read. A new-style arXiv id YYMM.NNNN dates a paper to the month 20YY-MM; otherwise Paper.year dates it to the year; otherwise it is undated. Dates are when the paper appeared, not when the code was written. Read 2026-11-22.

Repositories linked to this paper

Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.

Abstract

We introduce Language-Informed Latent Actions (LILA), a framework for learning natural language interfaces in the context of human-robot collaboration. LILA falls under the shared autonomy paradigm: in addition to providing discrete language inputs, humans are given a low-dimensional controller $-$ e.g., a 2 degree-of-freedom (DoF) joystick that can move left/right and up/down $-$ for operating the robot. LILA learns to use language to modulate this controller, providing users with a language-informed control space: given an instruction like "place the cereal bowl on the tray," LILA may learn a 2-DoF space where one dimension controls the distance from the robot's end-effector to the bowl, and the other dimension controls the robot's end-effector pose relative to the grasp point on the bowl. We evaluate LILA with real-world user studies, where users can provide a language instruction while operating a 7-DoF Franka Emika Panda Arm to complete a series of complex manipulation tasks. We show that LILA models are not only more sample efficient and performant than imitation learning and end-effector control baselines, but that they are also qualitatively preferred by users.

For agents

The same record, over MCP at https://syntology.ai/mcp:

get_harvested_code_for_paper("2111.03205")
get_code_for_paper("2111.03205")
have("2111.03205")

The run record, dated, one paper per request, free:

curl https://syntology.ai/api/ran/2111.03205.json

A badge for a README (the split and the date, never a ratio):

[![Syntology run record](https://syntology.ai/api/ran/2111.03205.svg)](https://syntology.ai/paper/2111.03205)

Connect an agent — have() is free.