The constraints listed here are sometimes called symbolic constraints. They are currently not reifiable. Unless documented otherwise, they maintain (at most) boundconsistency in their arguments; see The Constraint System.
count(
+Val,
+List,
+RelOp,
?Count)
deprecatedsum/3
constraint, one arithmetic
comparison, and several reified equalities.
count/4
maintains arcconsistency, but in practice, the
following constraint is a better alternative.
global_cardinality(
+Xs,
+Vals)
global_cardinality(
+Xs,
+Vals,
+Options)
If either Xs or Vals is ground, and in many other
special cases, global_cardinality/[2,3]
maintains
arcconsistency, but generally, boundconsistency cannot be
guaranteed. An arcconsistency algorithm [Regin 96] is used, roughly
linear in the total size of the domains.
Options is a list of zero or more of the following:
consistency(
Cons)
domain
on(dom)
. The default.
bound
on(minmax)
.
value
on(val)
.
on(
On)
dom
minmax
val
cost(
Cost,
Matrix)
consistency/1
option value.
A cost is associated with the constraint and reflected into the domain
variable Cost. Matrix should be a d*n
matrix, represented as a list of d lists, each of
length n. Assume that each Xi equals K(pi).
The cost of the constraint is then
Matrix[1,p1]+...+Matrix[d,pd].
With this option, an arcconsistency algorithm [Regin 99] is used, the complexity of which is roughly O(d(m + n log n)) where m is the total size of the domains.
element(
?X,
+List,
?Y)
Maintains arcconsistency in X and
boundconsistency in List and Y.
Corresponds to nth1/3
in library(lists)
.
relation(
?X,
+MapList,
?Y)
deprecated
ConstantRange pairs, where the integer
keys occur uniquely (see Syntax of Indexicals). True if
MapList contains a pair X
R and Y
is in the range denoted by R.
An arbitrary binary constraint can be defined with relation/3
.
relation/3
is implemented by straightforward transformation to
the following, more general constraint, with which arbitrary relations
can be defined compactly:
table(
+Tuples,
+Extension)
table(
+Tuples,
+Extension,
+Options)
For convenience, Extension may contain ConstantRange (see Syntax of Indexicals) expressions in addition to integers.
Options is a list of zero or more of the following. It can be used to control the waking and pruning conditions of the constraint:
consistency(
Cons)
domain
bound
value
table/[2,3]
is implemented in terms of
the following, more general constraint, with which arbitrary relations
can be defined compactly:
case(
+Template,
+Tuples,
+Dag)
case(
+Template,
+Tuples,
+Dag,
+Options)
Template is an arbitrary nonground Prolog term. Its variables are merely placeholders; they should not occur outside the constraint nor inside Tuples.
Tuples is a list of terms of the same shape as Template. They should not share any variables with Template.
Dag is a list of nodes of the form
node(
ID,
X,
Successors)
, where X is a
placeholder variable. The set of all X should equal the
set of variables in Template. The first node in the
list is the root node. Let rootID denote its ID.
Nodes are either internal nodes or leaf nodes. In the
former case, Successors is a list of terms
(
Min..
Max)
ID2, where the ID2 refers to a
child node. In the latter case, Successors is a list of
terms (
Min..
Max)
. In both cases, the
(
Min..
Max)
should form disjoint intervals.
ID is a unique, integer identifier of a node.
Each path from the root node to a leaf node corresponds to one set of tuples admitted by the relation expressed by the constraint. Each variable in Template should occur exactly once on each path, and there must not be any cycles.
Options is a list of zero or more of the following. It can be used to control the waking and pruning conditions of the constraint, as well as to identify the leaf nodes reached by the tuples:
leaves(
TLeaf,
Leaves)
on(
Spec)
prune(
Spec)
Spec is one of the following, where X is a placeholder variable occurring in Template or equal to TLeaf:
dom(
X)
min(
X)
max(
X)
minmax(
X)
val(
X)
none(
X)
The constraint holds if path(rootID,Tuple,Leaf) holds for each Tuple in Tuples and Leaf is the corresponding element of Leaves if given (otherwise, Leaf is a free variable).
path(ID,Tuple,Leaf) holds if Dag contains a term
node(
ID,
Var,
Successors)
, Var is the
unique k:th element of Template, i is the k:th
element of Tuple, and:
(
Min..
Max)
Child,
(
Min..
Max)
,
For example, recall that element(
X,
L,
Y)
wakes
up when the domain of X or the lower or upper bound of Y has
changed, performs full pruning of X, but only prunes the bounds of
Y. The following two constraints:
element(X, [1,1,1,1,2,2,2,2], Y), element(X, [10,10,20,20,10,10,30,30], Z)
can be replaced by the following single constraint, which is equivalent declaratively as well as wrt. pruning and waking. The fourth argument illustrates the leaf feature:
elts(X, Y, Z, L) : case(f(A,B,C), [f(X,Y,Z)], [node(0, A,[(1..2)1,(3..4)2,(5..6)3,(7..8)4]), node(1, B,[(1..1)5]), node(2, B,[(1..1)6]), node(3, B,[(2..2)5]), node(4, B,[(2..2)7]), node(5, C,[(10..10)]), node(6, C,[(20..20)]), node(7, C,[(30..30)])], [on(dom(A)),on(minmax(B)),on(minmax(C)), prune(dom(A)),prune(minmax(B)),prune(minmax(C)), leaves(_,[L])]).
The DAG of the previous example has the following shape:
elts/4
A couple of sample queries:
 ? elts(X, Y, Z, L). L in 5..7, X in 1..8, Y in 1..2, Z in 10..30  ? elts(X, Y, Z, L), Z #>= 15. L in 6..7, X in(3..4)\/(7..8), Y in 1..2, Z in 20..30  ? elts(X, Y, Z, L), Y = 1. Y = 1, L in 5..6, X in 1..4, Z in 10..20  ? elts(X, Y, Z, L), L = 5. Z = 10, X in(1..2)\/(5..6), Y in 1..2
all_different(
+Variables)
all_different(
+Variables,
+Options)
all_distinct(
+Variables)
all_distinct(
+Variables,
+Options)
Options is a list of zero or more of the following:
consistency(
Cons)
domain
all_distinct/[1,2]
and assignment/[2,3]
.
an arcconsistency algorithm [Regin 94] is used, roughly linear in the
total size of the domains. Implies on(dom)
.
bound
on(minmax)
.
value
all_different/[1,2]
. An algorithm achieving
exactly the same pruning as a set of pairwise inequality constraints is
used, roughly linear in the number of variables.
Implies on(val)
.
on(
On)
dom
all_distinct/[1,2]
and assignment/[2,3]
),
to wake up when the domain of a variable is changed;
min
max
minmax
val
all_different/[1,2]
), to wake up when a variable becomes ground.
nvalue(
?N,
+Variables)
all_distinct/2
.
The following is a constraint over two lists of length n of variables. Each variable is constrained to take a value in [1,n] that is unique for its list. Furthermore, the lists are dual in a sense described below.
assignment(
+Xs,
+Ys)
assignment(
+Xs,
+Ys,
+Options)
Options is a list of zero or more of the following, where
Boolean must be true
or false
(false
is the
default):
on(
On)
all_different/2
.
consistency(
Cons)
all_different/2
.
circuit(
Boolean)
true
, circuit(
Xs,
Ys)
must hold for the
constraint to be true.
cost(
Cost,
Matrix)
With this option, an arcconsistency algorithm [Sellmann 02] is used, the complexity of which is roughly O(n(m + n log n)) where m is the total size of the domains.
The following constraint can be thought of as constraining n nodes in a graph to form a Hamiltonian circuit. The nodes are numbered from 1 to n. The circuit starts in node 1, visits each node, and returns to the origin.
circuit(
+Succ)
circuit(
+Succ,
+Pred)
The following constraint can be thought of as constraining n tasks so that the total resource consumption does not exceed a given limit at any time:
cumulative(
+Tasks)
cumulative(
+Tasks,
+Options)
A task is represented by a term
task(
Oi,Di,Ei,Hi,Ti)
where Oi is the start
time, Di the nonnegative duration, Ei the end time,
Hi the nonnegative resource consumption, and Ti the
task identifier. All fields are domain variables with bounded
domains, or integers.
Let n be the number of tasks and L the global resource limit (by default 1, but see below), and:
Hij = Hi, if Oi =< j < Oi+Di Hij = 0 otherwise
The constraint holds if:
Options is a list of zero or more of the following, where
Boolean must be true
or false
(false
is the default).
limit(
L)
precedences(
Ps)
Ti
Tj#=
Dij
where Ti and Tj should be task identifiers, and Dij should be a a domain variable (or an integer), denoting:
OiOj = Dij and Dij in r
global(
Boolean)
true
, a more expensive algorithm will be used in order to
achieve tighter pruning of the bounds of the parameters.
This constraint is due to Aggoun and Beldiceanu [Aggoun & Beldiceanu 93].
The following constraint can be thought of as constraining n tasks to be placed in time and on m machines. Each machine has a resource limit, which is interpreted as a lower or upper bound on the total amount of resource used on that machine at any point in time that intersects with some task.
cumulatives(
+Tasks,
+Machines)
cumulatives(
+Tasks,
+Machines,
+Options)
A task is represented by a term
task(
Oi,Di,Ei,Hi,Mi)
where Oi is the start
time, Di the nonnegative duration, Ei the end time,
Hi the resource consumption (if positive) or production (if
negative), and Mi a machine identifier. All fields are domain
variables with bounded domains, or integers.
A machine is represented by a term machine(
Mj,Lj)
where Mj is the identifier and Lj is the resource
bound of the machine. Both fields must be integers.
Let there be n tasks and:
Hijm = Hi, if Mi=m and Oi =< j < Oi+Di Hijm = 0 otherwise
If the resource bound is lower
(the default), the constraint holds if:
If the resource bound is upper
, the constraint holds if:
Options is a list of zero or more of the following, where
Boolean must be true
or false
(false
is the
default):
bound(
B)
lower
(the default), each resource limit is treated
as a lower bound.
If upper
, each resource limit is treated
as an upper bound.
prune(
P)
all
(the default), the constraint will try to prune as many
variables as possible. If next
, only variables that
occur in the first nonground task term (wrt. the order
given when the constraint was posted) can be pruned.
generalization(
Boolean)
true
, extra reasoning based on assumptions on machine
assignment will be done to infer more.
task_intervals(
Boolean)
true
, extra global reasoning will be performed in an attempt
to infer more.
The following constraint captures the relation between a list of values, a list of the values in ascending order, and their positions in the original list:
sorting(
+Xs,
+Ps,
+Ys)
In practice, the underlying algorithm [Mehlhorn 00] is likely to achieve boundconsistency, and is guaranteed to do so if Ps is ground or completely free.
The following constraints model a set or lines or rectangles, respectively, so that no pair of objects overlap:
disjoint1(
+Lines)
disjoint1(
+Lines,
+Options)
Options is a list of zero or more of the following, where
Boolean must be true
or false
(false
is the
default):
decomposition(
Boolean)
true
, an attempt is made to decompose the constraint each time
it is resumed.
global(
Boolean)
true
, a redundant algorithm using global reasoning is used
to achieve more complete pruning.
wrap(
Min,
Max)
margin(
T1,
T2,
D)
sup
. If sup
is
used, all lines of type T2 must be placed before any line of type
T1.
This option interacts with the wrap/2
option in the sense that
distances are counted with possible wraparound, and the distance
between any end point and origin is always finite.
The file library('clpfd/examples/bridge.pl')
contains an example where
disjoint1/2
is used for scheduling nonoverlapping tasks.
disjoint2(
+Rectangles)
disjoint2(
+Rectangles,
+Options)
Options is a list of zero or more of the following, where
Boolean must be true
or false
(false
is the
default):
decomposition(
Boolean)
true
, an attempt is made to decompose the constraint each time
it is resumed.
global(
Boolean)
true
, a redundant algorithm using global reasoning is used
to achieve more complete pruning.
wrap(
Min1,
Max1,
Min2,
Max2)
inf
and sup
respectively. If they are integers, the space
in which the rectangles are placed should be thought of as a cylinder
wrapping around the X dimension where positions Min1 and
Max1 coincide. Furthermore, this option forces the domains of the
Xj variables to be inside [Min1,Max11].
Min2 and Max2 should be either integers or the atoms
inf
and sup
respectively. If they are integers, the space
in which the rectangles are placed should be thought of as a cylinder
wrapping around the Y dimension where positions Min2 and
Max2 coincide. Furthermore, this option forces the domains of the
Yj variables to be inside [Min2,Max21].
If all four are integers, the space is a toroid wrapping around both dimensions.
margin(
T1,
T2,
D1,
D2)
sup
. If
sup
is used, all rectangles of type T2 must be placed
before any rectangle of type T1 in the relevant dimension.
This option interacts with the wrap/4
option in the sense that
distances are counted with possible wraparound, and the distance
between any end point and origin is always finite.
synchronization(
Boolean)
true
, a redundant algorithm is used
to achieve more complete pruning for the following case:
The following example shows an artificial placement problem involving 25
rectangles including four groups of rectangles whose left and right
borders must be aligned. If Synch
is true
, it can be
solved with firstfail labeling in 23 backtracks. If Synch
is false
, 60 million backtracks do not suffice to solve it.
ex([O1,Y1a,Y1b,Y1c, O2,Y2a,Y2b,Y2c,Y2d, O3,Y3a,Y3b,Y3c,Y3d, O4,Y4a,Y4b,Y4c], Synch) : domain([Y1a,Y1b,Y1c, Y2a,Y2b,Y2c,Y2d, Y3a,Y3b,Y3c,Y3d, Y4a,Y4b,Y4c], 1, 5), O1 in 1..28, O2 in 1..26, O3 in 1..22, O4 in 1..25, disjoint2([t(1,1,5,1), t(20,4,5,1), t(1,1,4,1), t(14,4,4,1), t(1,2,3,1), t(24,2,3,1), t(1,2,2,1), t(21,1,2,1), t(1,3,1,1), t(14,2,1,1), t(O1,3,Y1a,1), t(O1,3,Y1b,1), t(O1,3,Y1c,1), t(O2,5,Y2a,1), t(O2,5,Y2b,1), t(O2,5,Y2c,1), t(O2,5,Y2d,1), t(O3,9,Y3a,1), t(O3,9,Y3b,1), t(O3,9,Y3c,1), t(O3,9,Y3d,1), t(O4,6,Y4a,1), t(O4,6,Y4b,1), t(O4,6,Y4c,1)], [synchronization(Synch)]).
The file library('clpfd/examples/squares.pl')
contains an example where
disjoint2/2
is used for tiling squares.
The following constraints express the fact that several vectors of domain variables are in ascending lexicographic order:
lex_chain(
+Vectors)
lex_chain(
+Vectors,
+Options)
Options is a list of zero or more of the following:
op(
Op)
#=<
(the default), the constraints
holds if Vectors are in nondescending lexicographic order. If
Op is the atom #<
, the constraints holds if
Vectors are in strictly ascending lexicographic order.
increasing
among(
Least,
Most,
Values)
Unless the increasing/0
or among/3
options are given,
the underlying algorithm [Carlsson & Beldiceanu 02] guarantees
arcconsistency.
The following constraint provides a general way of defining any constraint involving sequences whose checker, i.e. a procedure that classifies ground instances as solutions or nonsolutions, can be expressed by a nondeterministic finite automaton, extended with counter operations on its arcs. The point is that it is very much easier to come up with such a checker that to come up with a filtering algorithm for the constraint of interest.
automaton(...)
automaton/8
, you must call a constraint that
maps sequence to signature.
Abstract syntax:
ctr  ::= automaton( sequence, template, signature,
 
nodes, arcs,
 
counters, initial, final)
 
sequence  ::= list of template  {all of which of the same shape}

template  ::= term  {most general shape of the sequence}

{its variables should be local to ctr}
 
signature  ::= list of variable
 
nodes  ::= list of nodespec
 
nodespec  ::= source( node)  {an initial state}

 sink( node)  {an accept state}
 
node  ::= atomic
 
arcs  ::= list of arc  {all of which of the same shape}

arc  ::= arc( node, integer, node)  {from node, integer, to node}

 arc( node, integer, node, exprs)  {exprs correspond to new counter values}
 
 arc( node, integer, node, conditional)
 
conditional  ::= (cond > exprs)
 
 (conditional ; conditional)
 
exprs  ::= list of Expr  {of same length as counters}

{Expr as defined in Syntax of Arithmetic Expressions}
 
{over counters, template and constants}
 
{variables occurring in counters correspond to old counter values}
 
{variables occurring in template refer to the current element of sequence}
 
cond  ::= constraint  {over counters, template and constants}

{must be reifiable or true }
 
counters  ::= list of variable  {should be local to ctr}

initial  ::= list of integer  {of same length as counters}

final  ::= list of variable  {of same length as counters}


If no counters are used, the arguments counters, initial and
final should be []
. The arguments template and
sequence are only relevant if some Expr mentions a variable
in template, in which case the corresponding position in sequence
will be used at that point.
The constraint holds for a ground instance sequence if:
Here is an example.
Suppose that you want to define the predicate inflexion(
N,
L)
which should hold if L is a list of domain variables, and
N is the number of times that the sequence order switches between
strictly increasing and strictly decreasing. For example, the
sequence [1,1,4,8,8,2,7,1]
switches order three times.
Such a constraint is conveniently expressed by a finite automaton over
the alphabet [<,=,>]
denoting the order between consecutive
list elements. A counter is incremented when the order switches, and
is mapped to the first argument of the constraint. The automaton
could look as follows:
inflexion/2
The following piece of code encodes this using automaton/8
. The
auxiliary predicate inflexion_signature/2
maps the sequence to
a signature where the consecutive element order is encoded over the
alphabet [0,1,2]
. We use one counter with initial value 0 and
final value N (an argument of inflexion/2
).
Two transitions increment the counter.
All states are accept states.
inflexion(N, VARIABLES) : inflexion_signature(VARIABLES, SIGNATURE), automaton(_, _, SIGNATURE, [source(s),sink(i),sink(j),sink(s)], [arc(s,1,s ), arc(s,2,i ), arc(s,0,j ), arc(i,1,i ), arc(i,2,i ), arc(i,0,j,[C+1]), arc(j,1,j ), arc(j,0,j ), arc(j,2,i,[C+1])], [C],[0],[N]). inflexion_signature([], []). inflexion_signature([_], []) : !. inflexion_signature([VAR1,VAR2VARs], [SSs]) : S in 0..2, VAR1 #> VAR2 #<=> S #= 0, VAR1 #= VAR2 #<=> S #= 1, VAR1 #< VAR2 #<=> S #= 2, inflexion_signature([VAR2VARs], Ss).
A couple of queries:
 ? inflexion(N, [1,1,4,8,8,2,7,1]). N = 3 ? <RET> yes  ? length(L,4), domain(L,0,1), inflexion(2,L), labeling([],L). L = [0,1,0,1] ? ; L = [1,0,1,0] ? ; no
This constraint was introduced in [Beldiceanu, Carlsson & Petit 04].