Repository navigation
Tags
Tags
Correct the learned-heuristic timings, and say what gripper's seed does The README's transfer table quoted 0.038 / 0.561 / 0.169 seconds. The cache the published Research view renders from -- promo/rl-data.json, transfer_after -- says 0.0365 / 0.5337 / 0.1542. Expansions and costs in the same three rows match the cache exactly, so the wall-clock column alone came from a run nobody kept. A test pins the page to that cache; nothing pinned this table, so it drifted. generate_gripper takes a seed and, alone among the generators, never builds an rng from it: in gripper every ball starts in room A, so size and grippers determine the instance completely and the seed reaches only the problem name. Worth a docstring rather than a fix, because the trap is silent -- a train/test split that varies the seed at a fixed size hands you the same instance twice.
Publish the learned-heuristic results: a Research view in the workben… …ch (#161) jupyddl.learn shipped in 2.3.0 with its results living only in .docs/ and a video, so the published site said nothing about the largest addition in the release. The workbench now carries a Research view with the measured run: imitation against hff and goalcount, the per-instance spread behind the mean, the logistics loss and the exact reason for it, and the three claims that turned out to be wrong. Its numbers come from promo/rl-data.json, the cache the RL video renders from, so the page and the video quote one measured run and cannot drift apart. Tests pin that, and pin capabilities.json to the live registries. Rendering the view exposed a defect it did not cause: <main> was hidden until the worker reported ready, so every page of prose, the requirement matrix and the new view sat behind a spinner waiting for a 10 MB runtime none of them use. The shell now renders immediately from the committed bundle and only the run controls are gated on state.ready. Also carried: the GitHub Release job no longer requires the PyPI upload to have succeeded, and renovate no longer proposes bumping the workflows' Python pin.