You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Does the plan optimiser support action costs?
From looking at the code (src/sat/plan_optimizer.cpp), it seems that the length of the plan - in terms of number of actions - is optimised.
The text was updated successfully, but these errors were encountered:
you are correct, Lilotane only minimizes the number of actions (only if you use the option -of=-1, and by default just at the layer/depth where the initial plan was found). Handling integer-valued operator costs (i.e., cost that does not depend on an action's parameters) is something I've wanted to do for quite some time (it would be straight forward) but never got around to. Of course there's always the hacky approach to add k-1 dummy actions for each action of cost k ...
Are action/operator costs part of HDDL? Will they be? :)
Does the plan optimiser support action costs?
From looking at the code (src/sat/plan_optimizer.cpp), it seems that the length of the plan - in terms of number of actions - is optimised.
The text was updated successfully, but these errors were encountered: