Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated optimal plans for caldera #15

Open
3 tasks
haz opened this issue Jul 25, 2022 · 0 comments
Open
3 tasks

Updated optimal plans for caldera #15

haz opened this issue Jul 25, 2022 · 0 comments
Labels
Milestone

Comments

@haz
Copy link
Contributor

haz commented Jul 25, 2022

The optimal plans for the Caldera domain (released in the 2018 IPC) were computed by Patrik Haslum: caldera-sols.tar.gz

These should be added as solutions to the relevant problems (domains 131+143). These are just for the unsplit variant. All solutions were computed to be optimal, and this is the conversation snippet indicating as such:

I have found what should be optimal solutions to all
the instances of the caldera domain (opt and sat sets). The biggest
problem in the sat set took just over 20 minutes to solve (I think I can
trim that down a bit).

The domain is not quite delete-free (some actions have a negative
precondition (not (created ?v)) which is effectively "deleted" by adding
(created ?v)), but it's close enough to monotone that a small tweak to
my h+ solver was enough to make it generate valid plans for all
problems; since it's a relaxation, the plan costs should never be
greater than the optimal. (The grounding problem was trickier to deal
with...) The plan costs fall within the bounds you provided. In most
cases it's equal to your current upper bound, in a few cases it's one
action less.

Attaching the plan files (vlog.txt for each set is a summary of the
validator output, plus your bounds).

Update String

hsps/test_ilb -ce -flx -ho

TODO

  • Get optimal submission string
  • Update plans (/upper bound)
  • Update lower bounds w/ message string
@haz haz added the task label Jul 25, 2022
@haz haz added this to the 1.* milestone May 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant