Skip to content

Commit f06e13b

Browse files
[CI][Auto Version Bump] Compile changelog fragments (schedule)
Bumped packages: - isaaclab_teleop: 0.5.0 → 0.5.1
1 parent 482d21c commit f06e13b

4 files changed

Lines changed: 34 additions & 30 deletions

File tree

source/isaaclab/changelog.d/antoiner-docs-ensure-drives-exist.skip

Lines changed: 0 additions & 1 deletion
This file was deleted.

source/isaaclab_teleop/changelog.d/rwiltz-replay-stats-env-cfg.rst

Lines changed: 0 additions & 28 deletions
This file was deleted.

source/isaaclab_teleop/config/extension.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
[package]
22
# Semantic Versioning is used: https://semver.org/
3-
version = "0.5.0"
3+
version = "0.5.1"
44

55
# Description
66
title = "Isaac Lab Teleop"

source/isaaclab_teleop/docs/CHANGELOG.rst

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,39 @@
11
Changelog
22
---------
33

4+
0.5.1 (2026-05-22)
5+
~~~~~~~~~~~~~~~~~~
6+
7+
Added
8+
^^^^^
9+
10+
* Added an ``env_cfg`` block to ``teleop_replay_agent.py``'s stats output
11+
capturing the performance- and frame-timing-relevant env config inputs
12+
(``sim.dt``, ``sim.render_interval``, ``decimation``, ``episode_length_s``,
13+
``scene.num_envs``, ``sim.device``, ``sim.use_fabric``,
14+
``sim.render.antialiasing_mode``) along with precomputed ``policy_dt_s``,
15+
``render_dt_s``, ``renders_per_step``, ``target_policy_hz``, and
16+
``target_render_hz`` rates. The same fields are echoed in a compact
17+
``Env timing:`` line in the stdout summary so the measured
18+
``cpu_frame_time_ms`` / ``fps`` numbers are self-interpreting across
19+
machines and configs without cross-referencing the env definition.
20+
21+
Changed
22+
^^^^^^^
23+
24+
* Changed ``teleop_replay_agent.py``'s ``cpu_frame_time_ms`` and ``fps``
25+
blocks (both per-run and aggregate) to report on a **per-render** basis
26+
rather than per-``env.step``: each captured ``env.step`` CPU sample is
27+
divided by ``decimation / render_interval`` (the number of Kit renders
28+
per ``env.step``) before stats are computed. ``cpu_frame_time_ms.mean``
29+
now reads as the wall time between rendered frames and ``fps.mean``
30+
reads as the render rate -- the same number Kit's HUD shows, which is
31+
what the headset wearer / spectator actually perceives during real-time
32+
teleop. Field shapes and ``schema_version`` are unchanged. Falls back
33+
to the raw per-``env.step`` units when ``decimation`` or
34+
``render_interval`` are unavailable from the env config.
35+
36+
437
0.5.0 (2026-05-20)
538
~~~~~~~~~~~~~~~~~~
639

0 commit comments

Comments
 (0)