Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Built-in observation aggregators drop bounds-preserving specifications

未關閉
#560 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

@sylvesterkaczmarek 已經在處理了。

開始於 2026年9月28日。

  • #562 來自 @sylvesterkaczmarek —— 未關閉

評估

難度
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
分支
772
PR 合併指標
30 天內沒有已合併 PR

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  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 摘要。