Trace Format for Finite Domain Solvers
Repository of Problems and Traces
Pages in
progress quoted by 
This repository is a collection of
problems. Each problem is a subproject managed by a subproject
administrator. Each contributor becomes a subproject developer. The
pupose of a project is to build traces whose originality and interest
comes from various reasons: it reflects some particular property of the
used solver, or of a particular analysis tool, or it shows some
characteristics of the problem or of its resolution which help to
improve the solutions. Each project/problem shall follow a project
schema described here (to be done). To start a new project/program,
prepare a first instance of the project, then contact one of the
project administrator.
- illustrative problems : (pedagogical problems used to
help understanding aspects of
solvers, resolution or tools)
- classical problems (mostly academic problems,
including open instances, in order to find
the best ways to observe resolution)
- practical application problems :
(pratcical problems, not necessarily big, with the objective to show usefulness of tools)
Some other objectives of a problem/project may be:
- to find a bug (wrong, under or over constrained program). In this
case incorrect programs may also be studied in a project independently
from the cathegory.
- to improve resolution or to scale the program, showing how
the used tool and the kind of observation must be modified when
the instances grow.
- any objective which shows the usefulness of the tools for some
purpose, provided this objective can be comprehensively presented.