Installation

IBM ILOG Solver Debugger User's Manual > Debugging and Performance Tuning for Solver-based Applications > Installation

Installation

INDEX

PREVIOUS NEXT

In order to start using Solver Debugger, you need to know:

Prerequisites for Using Solver Debugger

To use the Debugger library, you need:

IBM® ILOG® Solver
IBM ILOG Concert

The only add-on for which specific features are supported is IBM ILOG Scheduler.

The Distribution Directories

The Solver Debugger and its add-on the Scheduler Debugger are to be installed in the same root directory as the Solver product and the Scheduler product respectively (typically ilog/solver and ilog/sched).

The distribution structure includes the following directories, where <solverdir> represents your Solver installation directory and <scheddir> your Scheduler installation:

<solverdir>/bin/<platform>/<libformat>

contains the Solver Debugger GUI, debugger.exe

<solverdir>/help

contains the online documentation

<solverdir>/examples/<platform>/<libformat>/debug*

contains C++ examples based on Solver

<solverdir>/examples/src/debug*

contains C++ source files for the examples

<solverdir>/include/ilsolver

contains the additional include files needed for using the debugger with Solver

<solverdir>/lib

contains the libraries ildebug.lib and ilsolverdebug.lib

<scheddir>/examples/<platform>/<libformat>/debug*

contains C++ examples based on Scheduler

<scheddir>/examples/src/debug*

contains C++ source files for the examples

<scheddir>/include/ilsched

contains the additional include files needed for using the debugger with Scheduler

<scheddir>/lib

contains the additional library ilschedulerdebug.lib

Examples Provided

Before using the Debugger facilities on your application, you can become familiar with them by testing the examples provided as part of the Solver Debugger distribution. All the examples contain Ilo objects.

To compile the examples on Solaris and Linux platforms, use the command:

make debuggersamples

in the directory:

<product>/examples/<platform>/<libformat>

Solver Examples

debugnqueen

This is a pure Solver C++ example. This well-known problem involves placing n queens on a chessboard in such a way that none of them can capture any other using the conventional moves allowed to a queen. In other words, the problem is to select n squares on a chessboard so that any pair of selected squares is never aligned, either vertically or horizontally. This example uses a Drawing Board to represent the chessboard.

debuggolomb

This example is well-suited to propagation analysis with different levels of pruning for the alldiff constraint. It is a good example of the use of the Christmas Tree and the Propagation Spy. The goal of the debuggolomb problem is to find a set of values representing the graduations of a rule such that the difference between each pair of graduations is always distinct, and such that the length of the rule is minimal.

debuglsknight

This example shows how to use the Debugger with local search. It consists in placing as few knights as possible on a chessboard in such a way that each square is controlled--attacked or occupied--by at least one knight.

debugpheasant

This example is useful for tracing the Initial Propagation. This problem consists in finding the number of pheasants and rabbits in a field, knowing that there are 20 heads and 56 legs overall.

Scheduler Example

debugjobshopm

The aim of this problem is to schedule a number of jobs on a set of machines in order to minimize completion time, called makespan. Each job is a sequence of tasks and each task represents a machine. This example enables you to see the Activity Domains window, the Gantt chart and specific scheduling events in the Propagation Spy. In the code of debugjobshopm you will find examples of conditional breakpoints, Debugger disabling, and the automatic result display switched off.

PREVIOUS NEXT