Differences between revisions 16 and 17
Revision 16 as of 2022-02-15 14:16:36
Size: 5012
Editor: XmlRpcBot
Comment:
Revision 17 as of 2022-03-21 15:10:56
Size: 5321
Editor: XmlRpcBot
Comment:
Deletions are marked like this. Additions are marked like this.
Line 67: Line 67:
state_equation_constraints() state_equation_constraints(verbosity=normal)
Line 69: Line 69:

 * ''verbosity'' ({silent, normal, verbose, debug}): Option to specify the verbosity level.
  * {{{silent}}}: only the most basic output
  * {{{normal}}}: relevant information to monitor progress
  * {{{verbose}}}: full output
  * {{{debug}}}: like verbose with additional debug output

Delete relaxation constraints

Operator-counting constraints based on the delete relaxation. By default the constraints encode an easy-to-compute relaxation of h+. With the right settings, these constraints can be used to compute the optimal delete-relaxation heuristic h+ (see example below). For details, see

delete_relaxation_constraints(use_time_vars=false, use_integer_vars=false)
  • use_time_vars (bool): use variables for time steps. With these additional variables the constraints enforce an order between the selected operators. Leaving this off (default) corresponds to the time relaxation by Imai and Fukunaga. Switching it on, can increase the heuristic value but will increase the size of the constraints which has a strong impact on runtime. Constraints involving time variables use a big-M encoding, so they are more useful if used with integer variables.

  • use_integer_vars (bool): restrict auxiliary variables to integer values. These variables encode whether operators are used, facts are reached, which operator first achieves which fact, and in which order the operators are used. Restricting them to integers generally improves the heuristic value at the cost of increased runtime.

Example: To compute the optimal delete-relaxation heuristic h+, use

operatorcounting([delete_relaxation_constraints(use_time_vars=true, use_integer_vars=true)], use_integer_operator_counts=true))

LM-cut landmark constraints

Computes a set of landmarks in each state using the LM-cut method. For each landmark L the constraint sum_{o in L} Count_o >= 1 is added to the operator-counting LP temporarily. After the heuristic value for the state is computed, all temporary constraints are removed again. For details, see

lmcut_constraints()

Posthoc optimization constraints

The generator will compute a PDB for each pattern and add the constraint h(s) <= sum_{o in relevant(h)} Count_o. For details, see

pho_constraints(patterns=systematic(2))

State equation constraints

For each fact, a permanent constraint is added that considers the net change of the fact, i.e., the total number of times the fact is added minus the total number of times is removed. The bounds of each constraint depend on the current state and the goal state and are updated in each state. For details, see

state_equation_constraints(verbosity=normal)
  • verbosity ({silent, normal, verbose, debug}): Option to specify the verbosity level.

    • silent: only the most basic output

    • normal: relevant information to monitor progress

    • verbose: full output

    • debug: like verbose with additional debug output

FastDownward: Doc/ConstraintGenerator (last edited 2022-03-21 15:10:56 by XmlRpcBot)