StanfordVL/BEHAVIOR-1K

Make ControllableObjectViewAPI unaccessible outside physics steps

Open

#2,028 opened on Mar 20, 2026

View on GitHub
 (0 comments) (0 reactions) (1 assignee)Python (222 forks)auto 404
buggood first issue

Repository metrics

Stars
 (1,604 stars)
PR merge metrics
 (PR metrics pending)

Description

Currently the ControllableObjectViewAPI supports features like clearing object caches etc. because it allows calls outside the physics step. We should remove that feature and instead rely on a check that makes sure it's only used during physics steps, where set_position cannot be called on objects.

Contributor guide

Research direction
Investigate where ControllableObjectViewAPI is called outside physics steps and add a check to enforce usage only during physics steps.
Tech stack
python
Domain
backend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Python
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70