Skip to content

fix(learn): honest ranking metrics, seed-sensitive generators, distinct benchmark configs - #171

Merged
guilyx merged 13 commits into
mainfrom
feat/zen-gates-g3lolk
Nov 3, 2026
Merged

guilyx merged 13 commits into
mainfrom
feat/zen-gates-g3lolk

Conversation

@guilyx

@guilyx guilyx commented Nov 3, 2026

Copy link
Copy Markdown
Member

What and why

This PR fixes the 12 verified findings from the review of jupyddl/learn, the generators and the benchmark harness. Several of them made a metric look better than it was.

Finding Before After
Ranking ties Counted as wins: a constant model scored top-1 = 1.0, and checkpoint selection preferred collapsed epochs Identical siblings are dropped. A tie with k siblings earns 1/(k+1). A constant model now scores chance (0.379)
"Held out" top-1 Computed over the training groups split keeps the held-out groups, and selection and reporting use them. The CLI says "held out" only when the groups really were
gripper and workshop generators Ignored the seed, so 20 seeds gave 1 distinct problem and tuning/validation/held-out sets were duplicates The seed varies the instance. The same seed still gives the same text
blocksworld and random-strips generators Could produce instances already solved at the start (75 of 200 blocksworld seeds at size 2) Re-rolled. Every other seed is byte-identical (checked on 200 seeds per size)
Malformed bundles Loaded without complaint, and the pure and NumPy paths disagreed Refused with a clear ValueError (shape, finiteness, keys)
set_flat Corrupted the model before raising Length is checked first
Negated facts All shared one feature slot (not) Keyed on not-<predicate>
DAgger/bootstrap split Leaked across train/validation Grouped on the base instance name
Benchmark configs wastar weight 1 and weight 5 were merged into one row; the heuristic recorded was the one asked for, not the one that ran config label includes the planner arguments; the heuristic that actually ran is recorded (api.resolve_heuristic)
summarise_transfer Averaged over solved runs only, so a heuristic that solved just the easy instance looked 45× better Unsolved runs are charged; mean_cost is over instances every configuration solved
train() Silently returned the initial weights when given nothing to rank Raises
learn_heuristic Consumed a generator passed as sizes, leaving nothing to iterate Size arguments are turned into lists on entry

Published research numbers

The published figures are left exactly as measured: they match rl-data.json, the Research view and the video. .docs/learned-heuristics.md and .docs/rl-for-search.md gain a dated Corrections, 2026-11-03 section, written in the style of the existing correction notes:

  • Top-1, re-measured (takes seconds): blocksworld 0.923 → 0.929; logistics 0.656 → 0.667; gripper 1.000 → 1.000.
    • The gripper 1.000 was not evidence: a constant model also scored 1.000, and its held-out instances duplicated the training ones.
  • Checkpoints moved: blocksworld now keeps epoch 12 instead of 20, and logistics epoch 22 instead of 9. The downstream figures came from different checkpoints and are marked "not re-measured".
  • The imitation-only "366 expansions" averaged only the 9 instances it solved. Charging the failure gives 6 329.

Behaviour changes to note

  • gripper/workshop: every generated instance changes. demos/workshop no longer matches generate, and the README now says so.
  • Learned models: a model trained on a domain with negative preconditions sees different features. The CHANGELOG says to retrain.

How it was checked

  • New tests: about 30 tests (54 cases) across test_learn.py, test_generator.py and test_benchmark.py. 44 of the new cases fail on the previous code; the rest are guards that must pass on both. They also pass with NumPy unavailable.
  • My own run after rebasing onto main: 569 passed, 1 skipped. flake8 and black are clean, and web/dist is rebuilt.

Checklist

  • flake8 jupyddl tests tools and pytest pass locally
  • python tools/build_web.py re-run; web/dist committed
  • No planner guarantee changes
  • CHANGELOG.md updated

The history has a merge -s ours of the already-merged #169 tip so the push fast-forwards. Squash-merge with the PR title.


Generated by Claude Code

claude added 13 commits November 2, 2026 21:26
Write down where and why we mean to publish jupyddl as citable research
software (.docs/PUBLISHING.md): a Zenodo DOI per release, a JOSS paper,
ICAPS workshops for the research results, with a readiness checklist, the
paper outline, the AI-usage disclosure JOSS requires, and how contributors
can be considered for authorship. The README states the project's aim and
its Cite section now says which version the 2021 preprint describes.

Add the community files an outside contributor expects: a security policy,
a pull-request template, a "Propose an algorithm" issue template, and an
"Adding an algorithm" section in CONTRIBUTING.md.

Run tests and build on pull requests. They were `on: [push]`, which never
fires for a fork, so a contributor's PR showed no checks at all.

Fix AGENTS.md drift: the Python floor is 3.10 and Mergify is retired.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014RbGtRHF8XhkiPQCDVHtV2
A package can now add planners, heuristics and generators by declaring
`jupyddl.planners`, `jupyddl.heuristics` or `jupyddl.generators` entry
points. Once installed, they work from the CLI, the benchmark harness and
`jupyddl.solve` by name, without anyone importing the package.

Discovery is lazy and defensive (jupyddl/plugins.py): the CLI runs it
before building its parser, the library only on a registry miss, so
importing jupyddl never scans installed packages. A built-in name always
wins, a plugin that fails to import is skipped with a warning, and
JUPYDDL_NO_PLUGINS=1 turns it off. `jupyddl plugins` lists what was found.
The CLI now reads `requires_heuristic` from the registry at call time,
since INFORMED_PLANNERS is fixed at import and cannot know about plugins.

.docs/EXTENDING.md walks through a heuristic, a planner from a priority
function, a planner from scratch with the budget/observer contract, a
generator, testing the guarantees you claim, and shipping as a plugin.
tests/test_extending.py runs every Python block in it, so it cannot drift.

best_first now accepts a tuple priority for tie-breaking; observers get
its first element as `f`, so traces stay numeric.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014RbGtRHF8XhkiPQCDVHtV2
# Conflicts:
#	.docs/PUBLISHING.md
#	AGENTS.md
#	CHANGELOG.md
Each of these returned a plan, a cost or a value without complaint, and
validate_plan accepted the plans because it replays them through the same
Task.apply. tests/test_semantics.py now pins them on tiny hand-written
tasks; 16 of its cases fail on the previous code.

- Derived facts were never retracted, and (not <derived>) held from the
  start. close() now recomputes axioms from scratch and maintains negated
  derived facts; negation inside a rule body (needs stratification) is
  refused. The relaxation gets the complement for free, so it never calls
  a solvable state a dead end.
- An atom both added and deleted left its complement true too; a `when`
  re-adding a deleted atom did the same. Complements: the delete wins.
- Under a (total-cost) metric an action without a cost effect is free, as
  in IPC planners (pegsol/sokoban optimised the wrong objective). Cost
  inside `when` was charged unconditionally: refused, as are negative costs.
- A never-defined numeric fluent read as 0; conditions reading one fail.
- blind skipped zero-cost actions and overestimated.
- h1/h2/hm crashed on numeric states; LM-cut crashed on an empty goal.
- lmcut and h2 clear `admissible` on tasks with conditional effects.
- Optimal planners default to lmcut, not hff; `-H none` means blind.
- make_heuristic builds a heuristic class or partial instead of passing it
  through unbuilt.
- Fact ids and id sets are built in sorted order, so LM-cut tie-breaks,
  expansions and plans no longer change with PYTHONHASHSEED.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014RbGtRHF8XhkiPQCDVHtV2
- iddfs, idastar and ehc never read their budget, so --time-limit was
  ignored. They poll per expansion now; the recursive ones unwind with
  BudgetExhausted. beam polls per node, not per layer, and bnb stops
  evaluating siblings once the budget fires.
- Hitting a depth cap (iddfs max_depth, bnb max_depth) or Python's
  recursion limit sets stats.truncated: it is not a proof of
  unsolvability, nor of optimality.
- bfs and iddfs leave OPTIMAL_PLANNERS: they minimise plan length, and on
  errands return cost 16 where 10 is optimal.
- Live dashboard: a budget stop no longer reads "no plan found"; lines are
  clipped to the stream's terminal width so repaints do not smear; the
  non-tty log writes at most every two seconds.
- idastar/ehc/hc/beam without a heuristic raise a clear ValueError;
  MultiObserver forwards positional arguments; the SearchObserver and
  best_first docstrings say what actually happens.

tests/test_search_contract.py runs every planner where the budget is the
only thing that stops it, checks OPTIMAL_PLANNERS against dijkstra under
action costs, and pins the dashboard behaviour.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014RbGtRHF8XhkiPQCDVHtV2
- Exit codes say what happened: 0 solved, 1 no plan, 2 bad input, 3
  stopped by a budget, 4 a plan that failed validation. Unsolvable, out of
  budget and a crash all used to exit 1.
- Bad input (missing file, parse error, unknown planner or heuristic, a
  malformed --sizes) is one line on stderr, not a traceback;
  JUPYDDL_DEBUG=1 restores the traceback. --version exists.
- `demo` and `benchmark demos` never finished. Both stop each search after
  10 s by default (--time-limit 0 for none); animate and demo take the
  same budget flags as solve.
- benchmark validates --planners/--heuristic/--metric up front, and chart
  options check for the viz extra before searching rather than after.
- Dead ends (h = inf) crashed the progress chart and coloured the
  wavefront NaN; in the workbench they made the progress message invalid
  JSON and aborted the run.
- A trace's plan is the visible plan, without compiler bookkeeping.
- Packaging: the sdist's own suite failed because .github/ was dropped
  wholesale; only workflows are excluded now. build runs twine --strict.
  black is pinned to one major in dev and format.yml; Renovate pins
  third-party actions to digests.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014RbGtRHF8XhkiPQCDVHtV2
PR titles become Conventional Commits (pr-title check, plain shell, no
third-party action). On every push to main release-please keeps one release
PR whose version follows from what was merged: fix -> patch, feat -> minor,
feat!/BREAKING CHANGE -> major. tools/release_pr_fixup.py then files the
hand-written [Unreleased] notes under the new section and rebuilds web/dist,
which records the version.

Merging the release PR tags the commit; release-please.yml then dispatches
release.yml on the tag, because a tag made with the workflow token triggers
no workflows. release.yml now also refuses a dispatch that would re-release
an existing version. Renovate opens semantic titles so its PRs pass the check.

tests/test_release.py pins the manifest, pyproject and __version__ together
and checks the changelog fix-up, including the section release.yml extracts.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014RbGtRHF8XhkiPQCDVHtV2
…ct benchmark configs

- Ranking ties counted as wins, so a constant model scored top-1 = 1.0 and
  checkpoint selection preferred collapsed epochs. Identical siblings are
  dropped and a tie with k siblings earns 1/(k+1).
- "Held out" top-1 used training groups; split now keeps the held-out
  groups and selection/reporting use them.
- gripper and workshop ignored the seed, so tuning, validation and held-out
  sets were duplicates. The seed now varies the instance.
- blocksworld and random-strips could generate instances already solved
  at the start; those seeds are re-rolled, every other seed is unchanged.
- Malformed heuristic bundles are refused on load; set_flat is atomic;
  negated facts key on not-<predicate>; DAgger/bootstrap samples split
  with their base instance; pure ranking without groups raises;
  learn_heuristic accepts generators for its size arguments.
- Benchmark rows carry a config label including planner arguments and
  record the heuristic that actually ran (api.resolve_heuristic).
- summarise_transfer charges unsolved runs instead of averaging over
  solved ones only.

Published figures are left as measured; .docs/learned-heuristics.md and
rl-for-search.md carry dated corrections saying what each one measured.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014RbGtRHF8XhkiPQCDVHtV2
@guilyx
guilyx marked this pull request as ready for review November 3, 2026 08:49
@guilyx
guilyx merged commit e6ba76f into main Nov 3, 2026
11 checks passed
guilyx pushed a commit that referenced this pull request Nov 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants