1995
DOI: 10.1007/3-540-60299-2_13
|View full text |Cite
|
Sign up to set email alerts
|

Debugging constraint programs

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
12
0

Year Published

2000
2000
2015
2015

Publication Types

Select...
6
2

Relationship

0
8

Authors

Journals

citations
Cited by 25 publications
(12 citation statements)
references
References 1 publication
0
12
0
Order By: Relevance
“…14 indicates that the swap between the variables (3,9) and (3,17) removes existing conflicts in columns 9 and 17 and introduces a new conflict in column 17. In turn, Fig.…”
Section: Model Concepts and Their Operationsmentioning
confidence: 99%
See 1 more Smart Citation
“…14 indicates that the swap between the variables (3,9) and (3,17) removes existing conflicts in columns 9 and 17 and introduces a new conflict in column 17. In turn, Fig.…”
Section: Model Concepts and Their Operationsmentioning
confidence: 99%
“…It led to some exciting developments such as the Grace debugger [9], the visualization of search trees (e.g., [3,10,11,17]), global constraints (e.g., [2,6,12]), the effect of propagation on the variable domains (e.g., [11,17]) and the DISCiPl project [4]. High-level visualization tools are desirable for at least two reasons.…”
Section: Introductionmentioning
confidence: 99%
“…While the focus of this paper is tree search visualisation, it is important to note that there has been significant work in related areas such as matrix-based visualisations of the variables and/or their domains (e.g. [3,6,14,22,27]), visualisation of the constraint-network (e.g. [16,17,24]), and problem-specific and/or custom visualisations (e.g.…”
Section: Related Workmentioning
confidence: 99%
“…For constraint programs the existing profiling tools (e.g. [1,3,8,11,14,18,21,22]) mostly focus on visualising the search tree (for those based on tree-search), visualising constraints and variables and their domains, showing solutions or gathering crude aggregate measures. While these tools can provide very useful information, they are also somewhat limited.…”
Section: Introductionmentioning
confidence: 99%
“…The most used approach to debug programs in a standard programming language is by tracing, i.e., executing the program step by step, while inspecting the values variables get. Also, debugging by tracing has proven to be useful in many declarative programming contexts such as Prolog [18,4], Haskell [16], ILP [21], constraint programming [14] and deductive databases [10]. This suggests to debug MX theories by tracing an MX solver.…”
Section: Introductionmentioning
confidence: 99%