Trace number 280735

Some explanations

A solver is run under the control of another program named runsolver. runsolver is in charge of imposing the CPU time limit and the memory limit to the solver. It also monitors some information about the process. The trace of the execution of a solver is divided into four (or five) parts:
  1. SOLVER DATA
    This is the output of the solver (stdout and stderr).
    Note that some very long lines in this section may be truncated by your web browser ! In such a case, you may want to use the "Download as text" link to get the trace as a text file.

    When the --timestamp option is passed to the runsolver program, each line output by the solver is prepended with a timestamp which indicates at what time the line was output by the solver. Times are relative to the start of the program, given in seconds, and are wall clock time (not CPU time).

    As some 'v lines' may be very long (sometimes several megabytes), the 'v line' output by your solver may be split on several lines to help limit the size of the trace recorded in the database. In any case, the exact output of your solver is preserved in a trace file.
  2. VERIFIER DATA
    The output of the solver is piped to a verifier program which will search a value line "v " and, if found, will check that the given interpretation satisfies all constraints.
  3. CONVERSION SCRIPT DATA (Optionnal)
    When a conversion script is used, this section shows the messages that were output by the conversion script.
  4. WATCHER DATA
    This is the informations gathered by the runsolver program. It first prints the different limits. There's a first limit on CPU time set to X seconds (see the parameters in the trace). After this time has ellapsed, runsolver sends a SIGTERM and 2 seconds later a SIGKILL to the solver. For safety, there's also another limit set to X+30 seconds which will send a SIGXPU to the solver. The last limit is on the virtual memory used by the process (see the parameters in the trace).
    Every ten seconds, the runsolver process fetches the content of /proc/loadavg, /proc/pid/stat and /proc/pid/statm (see man proc) and prints it as raw data. This is only recorded in case we need to investigate the behaviour of a solver. The memory used by the solver (vsize) is also given every ten seconds.
    When the solver exits, runsolver prints some informations such as status and time. CPU usage is the ratio CPU Time/Real Time.
  5. LAUNCHER DATA
    These informations are related to the script which will launch the solver. The most important informations are the command line given to the solver, the md5sum of the different files and the dump of the /proc/cpuinfo and /proc/meminfo which provides some useful information on the computer.

Solver answer on this benchmark

Solver NameAnswerCPU timeWall clock time
aolibpvo 2007-01-17OPTIMUM 0.099984 0.11211

General information on the benchmark

NameMaxCSP/planning/
mprime03ac_ext.xml
MD5SUM7dba53adfc9212d0847f5337f5f1e049
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkMOPT
Best Number of satisfied constraints622
Best CPU time to get the best result obtained on this benchmark0.099984
Satisfiable
(Un)Satisfiability was proved
Number of variables50
Number of constraints625
Maximum constraint arity2
Maximum domain size10
Number of constraints which are defined in extension625
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Quality of the solution as a function of time


Download the above graph as a PDF file / as an EPS file

Solver Data (download as text)

0.10	
0.10	s SATISFIABLE
0.10	o 167
0.10	v 2 1 1 0 1 0 0 0 2 0 1 0 1 0 1 1 1 1 1 1 0 0 0 0 0 0 0 1 1 0 0 1 1 1 0 0 1 1 1 1 1 1 1 1 1 1 0 1 1 -1
0.10	s SATISFIABLE
0.10	o 171
0.10	v 2 1 1 0 1 0 0 0 2 0 1 0 1 0 1 1 1 1 1 1 0 0 0 0 0 0 0 1 1 0 0 1 1 1 0 0 1 1 1 1 1 1 1 1 1 0 0 1 1 -1
0.10	s SATISFIABLE
0.10	o 172
0.10	v 2 1 1 0 1 0 0 0 2 0 1 0 1 0 1 1 1 1 1 1 0 0 0 0 0 0 0 0 1 2 0 1 1 1 0 0 1 1 1 1 1 1 1 1 1 0 0 0 1 -1
0.10	s SATISFIABLE
0.10	o 173
0.10	v 2 1 1 0 1 0 0 0 2 0 1 0 1 0 1 1 1 1 1 1 0 0 0 0 0 0 0 1 0 0 0 1 1 1 0 0 1 1 1 1 1 1 1 1 1 0 0 1 0 -1
0.10	s SATISFIABLE
0.10	o 175
0.10	v 2 1 1 0 1 0 0 0 2 0 1 0 1 0 0 1 1 1 1 1 0 0 0 0 0 0 0 1 0 0 0 1 1 1 0 0 1 1 1 1 1 1 1 1 1 0 0 1 0 -1
0.10	s SATISFIABLE
0.10	o 176
0.10	v 2 1 1 0 1 0 0 0 0 0 1 0 1 0 0 1 1 1 1 1 0 0 0 0 0 0 0 1 0 0 0 1 1 1 0 0 1 1 1 1 1 1 1 1 1 0 0 1 0 -1
0.10	s SATISFIABLE
0.10	o 177
0.10	v 0 1 1 0 1 0 0 0 2 0 0 0 1 0 0 1 1 1 1 1 0 0 0 0 0 0 0 1 0 0 0 1 1 1 0 0 1 1 1 1 1 1 1 1 1 0 0 1 0 -1
0.10	s SATISFIABLE
0.10	o 178
0.10	v 0 1 1 0 1 0 0 0 0 0 0 0 1 0 0 1 1 1 1 1 0 0 0 0 0 0 0 1 0 0 0 1 1 1 0 0 1 1 1 1 1 1 1 1 1 0 0 1 0 -1
0.10	s SATISFIABLE
0.10	o 180
0.10	v 0 1 1 0 1 0 0 0 0 0 0 0 1 0 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 0 0 1 1 1 1 1 1 1 1 1 0 0 0 0 -1
0.10	s SATISFIABLE
0.10	o 181
0.10	v 1 0 0 0 0 1 0 0 0 0 0 1 0 0 0 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 0 0 1 1 1 1 1 1 1 1 1 0 0 0 0 -1
0.10	s SATISFIABLE
0.10	o 182
0.10	v 1 0 0 0 0 0 0 0 0 0 0 1 0 0 0 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 0 1 1 1 1 1 1 1 1 1 0 0 0 0 -1
0.10	o 182
0.10	v 1 0 0 0 0 0 0 0 0 0 0 1 0 0 0 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 0 1 1 1 1 1 1 1 1 1 0 0 0 0 -1
0.10	s OPTIMUM FOUND
c 
c 
c 
c conversion script
c 
c 

parsing "/tmp/evaluation/280735-1169307553/unknown.xml" file ... done.
writing "/tmp/evaluation/280735-1169307553/unknown.wcsp" file ... done.

Verifier Data (download as text)

3 unsatisfied constraints, 622 satisfied constraints

Watcher Data (download as text)

runsolver version 3.1.3 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node2/watcher-280735-1169307553 -o ROOT/results/node2/solver-280735-1169307553 -C 2400 -M 900 /tmp/evaluation/280735-1169307553/aolibpvo /tmp/evaluation/280735-1169307553/unknown.wcsp 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 2400 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 2430 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 921600 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 972800 KiB
Current StackSize limit: 10240 KiB

/proc/loadavg: 1.95 2.00 2.00 5/87 26937
/proc/meminfo: memFree=689472/2055920 swapFree=4180552/4192956
[pid=26936] ppid=26934 vsize=18540 CPUtime=0
/proc/26936/stat : 26936 (runsolver) R 26934 26936 26873 0 -1 4194368 16 0 0 0 0 0 0 0 20 0 1 0 279150985 18984960 279 18446744073709551615 4194304 4267372 548682069072 18446744073709551615 206381313319 0 0 4096 24578 0 0 0 17 1 0 0
/proc/26936/statm: 4635 279 244 17 0 2626 0

Child status: 0
Real time (s): 0.11211
CPU time (s): 0.099984
CPU user time (s): 0.097985
CPU system time (s): 0.001999
CPU usage (%): 89.1838
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.097985
system time used= 0.001999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 409
page faults= 0
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 8
involuntary context switches= 4

runsolver used 0.001999 s user time and 0.008998 s system time

The end

Launcher Data (download as text)

Begin job on node2 on Sat Jan 20 15:39:13 UTC 2007


IDJOB= 280735
IDBENCH= 11930
IDSOLVER= 60
FILE ID= node2/280735-1169307553

PBS_JOBID= 3609942

Free space on /tmp= 66045 MiB

SOLVER NAME= aolibpvo 2007-01-17
BENCH NAME= HOME/pub/bench/CPAI06/MaxCSP/planning/mprime03ac_ext.xml
COMMAND LINE= /tmp/evaluation/280735-1169307553/aolibpvo /tmp/evaluation/280735-1169307553/unknown.wcsp
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node2/convwatcher-280735-1169307553 -o ROOT/results/node2/conversion-280735-1169307553 -C 600 -M 900 python xcsp2wcsp.py /tmp/evaluation/280735-1169307553/unknown.xml
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node2/watcher-280735-1169307553 -o ROOT/results/node2/solver-280735-1169307553 -C 2400 -M 900  /tmp/evaluation/280735-1169307553/aolibpvo /tmp/evaluation/280735-1169307553/unknown.wcsp

META MD5SUM SOLVER= b8e99429ba4d9a99d2bd28d3d95367aa
MD5SUM BENCH=  7dba53adfc9212d0847f5337f5f1e049

RANDOM SEED= 356733571

TIME LIMIT= 2400 seconds

MEMORY LIMIT= 900 MiB


/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	:                   Intel(R) Xeon(TM) CPU 3.00GHz
stepping	: 3
cpu MHz		: 3000.259
cache size	: 2048 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5931.00
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	:                   Intel(R) Xeon(TM) CPU 3.00GHz
stepping	: 3
cpu MHz		: 3000.259
cache size	: 2048 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5586.94
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:        689952 kB
Buffers:         49320 kB
Cached:        1174788 kB
SwapCached:        572 kB
Active:         215528 kB
Inactive:      1064556 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        689952 kB
SwapTotal:     4192956 kB
SwapFree:      4180552 kB
Dirty:            2328 kB
Writeback:           0 kB
Mapped:          69552 kB
Slab:            70600 kB
Committed_AS:  7788592 kB
PageTables:       2420 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66045 MiB



End job on node2 on Sat Jan 20 15:39:14 UTC 2007