Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Built-in observation aggregators drop bounds-preserving specifications

未关闭
#560 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
75/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
python
领域
backend

调研方向

Start by locating base.AGGREGATORS and Updater.observation_spec(), then reproduce the AttributeError and the bounded Generic observable case described in the issue. Check that min, max, mean and median retain scalar or per-element bounds while sum remains unbounded, without changing value, shape/dtype, custom-aggregator or unbounded-input behavior.

由索引模型根据 Issue 内容生成。

描述

Reproduction

Built-in observation aggregators declare a bounds_reserving attribute, while Updater.observation_spec() reads preserves_bounds. Consequently, even min, max, mean and median are treated as having unknown bound behavior: the updater logs a warning and returns an unbounded Array instead of retaining a BoundedArray specification.

The problem is visible directly:

from dm_control.composer.observation.observable import base
assert base.AGGREGATORS['mean'].preserves_bounds is True
# AttributeError: functools.partial has no attribute preserves_bounds

A bounded Generic observable reduced with the built-in mean loses its limits through the actual Updater. Returned values remain in bounds, but the resulting specification no longer rejects out-of-bounds inputs.

Expected behavior

Use the attribute name already documented and consumed by Updater. The four bounds-preserving reducers should retain scalar or per-element limits, while sum must remain unbounded. Preserve reduced values, shape/dtype inference, custom-aggregator behavior and unbounded inputs.

Reproduced on main at a04e3e4cf56c12117d2294bb090f9acec21e5c67, including a native MuJoCo observation sequence. No renderer, external services or model inference is needed.

主要语言
Python
星标
4.7k
派生
765
PR 合并指标
30 天内没有已合并 PR

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

google-deepmind/dm_control 的其他 Issue

查看 google-deepmind/dm_control 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。