Track backtracking in Explicit Stack Search. #57
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rpgoldman
force-pushed
the
track-backtracks
branch
from
308a151
to
90f5304
Compare
rpgoldman
force-pushed
the
track-backtracks
branch
from
90f5304
to
a902404
Compare
Keep backtrack count in new special variable `*backtracks*`, and add it to `print-stats`. Fix format string typo. Remove a debug print that was left in. Redirect output from ESS to OUT-STREAM. Previously, output redirection was not propagated from `find-plans-stack` to `seek-plans-stack`.
Any time `seek-plans-stack` is called, it must be done in a context where a large number of special variables for counting (for assessing performance) are bound. Establish `bind-count-variables` macro for this purpose. Note that it is the *caller's* job to handle this -- it's already done by `find-plans-stack`, but any new call direct to `seek-plans-stack` will need to be wrapped.
Multiple minor clean-ups and optimizations spurred by SBCL compiler notes. Theorem-prover cleanup.
Incorrect multi-problem approach. Fix handling of logistics problems. Other domains have 1 problem per file, but logistics has multple problems per file, so this run script was not working properly.
Now applies to symbols (it's just an identity function there). This allows the programmer to work with problem names and problems interchangeably.
rpgoldman
force-pushed
the
track-backtracks
branch
from
a902404
to
0f96080
Compare
Instead of tracking each backtrack point, track only the point at which backtracking commenced, and then stop counting backtrack types until after we resume forward motion. So this means we will have a large number of backtrack counts, but a smaller number of counts of places where backtracking starts.
For whatever reason, pfile3 cannot be solved. (There's clearly some bug, probably in the domain design, because it fails instead of going away forever.) Also, when fixing that, made this more robust by using `asdf:system-relative-pathname`, instead of hard-coded pathname.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In order to identify opportunities for improving plan repair and developing analogical replay, collect statistics about backtracking.