Skip to content

Fix issue 177: returning plan trees from multiple plans - #199

Merged
rpgoldman merged 8 commits into
masterfrom
fix-177
May 6, 2026
Merged

rpgoldman merged 8 commits into
masterfrom
fix-177

Conversation

@rpgoldman

Copy link
Copy Markdown
Contributor

The logic for copying plan trees, to avoid issues with multiple plan tree returns, was incorrect. H/T to @mpatsift for finding this.

Note that this is being fixed for the enhanced plan trees returned by find-plans-stack.

The copying is subtle because the tasks in the plan tree share structure with the tasks in the plan.

Fixes #177

@rpgoldman
rpgoldman requested a review from mpatsift May 5, 2026 18:57
@rpgoldman rpgoldman self-assigned this May 5, 2026
@rpgoldman

Copy link
Copy Markdown
Contributor Author

When the tests pass (they pass on Allegro locally), I will clean up the history and merge

rpgoldman and others added 7 commits May 5, 2026 15:14
The translation table (for making a copy of an extended-plan-tree)
assumed that it would always be translating actual plan tree nodes.
But in dependency links there may appear a "pseudo-node", the symbol
`:init`, and this was not handled correctly.
All PDDL domains implicitly have the top type, `object` defined.  This
was previously not enforced.
Finding k plans is a hybrid of `:which :all` and `:which :first`.  Fix the handling of k plans (`plan-num-limit`) in `make-plan-return`.
The `expanded-task` fields of these structures need to be correctly
translated; previously only the `task` field was.
@rpgoldman
rpgoldman merged commit 05ab07b into master May 6, 2026
4 checks passed
@rpgoldman
rpgoldman deleted the fix-177 branch May 6, 2026 00:03
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.

Problems collecting multiple plan trees (find-plans-stack)

1 participant