Trace number 32763

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 NameAnswerObjective functionCPU timeWall clock time
wildcat-skc 0.8.0OPT-174776 0.006998 0.00841206

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/reduced/mps-v2-20-10/www.csit.fsu.edu/
~burkardt/datasets/mps/normalized-reduced-mps-v2-20-10-nazareth.opb
MD5SUM0bd58fd61104d4efa74fac2638f06649
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark-174776
Best CPU time to get the best result obtained on this benchmark0.002998
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function -174776
Optimality of the best value was proved YES
Number of variables78
Total number of constraints3
Number of constraints which are clauses0
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints3
Minimum length of a constraint17
Maximum length of a constraint61
Number of terms in the objective function 78
Biggest coefficient in the objective function 174756
Number of bits for the biggest coefficient in the objective function 18
Sum of the numbers in the objective function 524343
Number of bits of the sum of numbers in the objective function 20
Biggest number in a constraint 174759
Number of bits of the biggest number in a constraint 18
Biggest sum of numbers in a constraint 524343
Number of bits of the biggest sum of numbers20
Number of products (including duplicates)0
Sum of products size (including duplicates)0
Number of different products0
Sum of products size0

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.00	c 
0.00	c wildcat-skc (VERSION 0.8.0-lite-skc-devel)
0.00	c Developed by L. Liu  and M. Truszczynski 
0.00	c Last built on Tue 23 May 2006 09:27:47 PM EDT
0.00	c 
0.00	c ROOT/solvers/PB/PB06final/user3/wildcat-skc ROOT/tmp/node68/32763-1149274317/instance-32763-1149274317.opb 962173404 
0.00	c =================================== BEGIN ===================================
0.00	c 
0.00	c Random Number Seed: 962173404
0.00	c Noise: 0.1 (10 : 100) 
0.00	c Starting searching:
0.00	c Phase 1 ...
0.00	c   trying 349567: vc 
0.00	o 48215
0.00	c   trying -26116: vc 
0.00	o -59295
0.00	c   trying -97790: vc 
0.00	o -173682
0.00	c   trying -174048: vc 
0.00	o -174775
0.00	c   trying -174776: vc 
0.00	o -174775
0.00	c Phase 2 ...
0.00	c Phase 3 ...
0.00	s OPTIMUM FOUND
0.00	v -x1 -x2 -x3 -x4 -x5 -x6 -x7 -x8 -x9 -x10 -x11 -x12 -x13 -x14 -x15 -x16 -x17 x18 x19 x20 x21 x22 x23 x24 x25 x26 x27 x28 x29 x30 x31
0.00	v x32 x33 x34 x35 x36 x37 x38 x39 x40 x41 x42 x43 x44 x45 x46 x47 -x48 -x49 -x50 -x51 -x52 -x53 -x54 -x55 -x56 -x57 -x58 -x59 -x60 -x61
0.00	v -x62 -x63 -x64 -x65 -x66 -x67 -x68 -x69 -x70 -x71 -x72 -x73 -x74 -x75 -x76 -x77 -x78
0.00	c Total Number of Positive Atoms : 30
0.00	c 
0.00	c During searching:         0.004867 seconds elapsed.
0.00	c CPU time spent:           0 seconds.
0.00	c 
0.00	c =================================== END =====================================
0.00	c

Verifier Data (download as text)

OK	-174776

Watcher Data (download as text)

Enforcing CPU limit (will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime (will send SIGXCPU) limit: 1830 seconds
Enforcing Stack size limit: 67108864 bytes
Enforcing memory limit (will send SIGKILL): 1843200 Kb
Enforcing VSIZE limit: 1887436800 bytes
runsolver version 3.0.0 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node68/watcher-32763-1149274317 -o ROOT/results/node68/solver-32763-1149274317 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user3/wildcat-skc ROOT/tmp/node68/32763-1149274317/instance-32763-1149274317.opb 962173404 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.93 0.95 0.90 2/64 13674
/proc/meminfo: memFree=1681680/2055920 swapFree=4182316/4192956
[pid=13674] ppid=13672 vsize=5968 CPUtime=0
/proc/13674/stat : 13674 (wildcat-skc) R 13672 13674 13628 0 -1 4194304 166 0 0 0 0 0 0 0 18 0 1 0 193101208 6111232 149 18446744073709551615 134512640 135438821 4294956656 18446744073709551615 134605219 0 0 4096 16386 0 0 0 17 1 0 0
/proc/13674/statm: 1492 149 117 226 0 1263 0

Child status: 0
Real time (s): 0.00841206
CPU time (s): 0.006998
CPU user time (s): 0.005999
CPU system time (s): 0.000999
CPU usage (%): 83.1901
Max. virtual memory (cumulated for all children) (Kb): 0

Launcher Data (download as text)

Begin job on node68 on Fri Jun  2 18:51:57 UTC 2006


FILE ID= 32763-1149274317

PBS_JOBID= 299105

BENCH NAME= ROOT/tmp/node68/32763-1149274317/instance-32763-1149274317.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user3/wildcat-skc ROOT/tmp/node68/32763-1149274317/instance-32763-1149274317.opb 962173404
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node68/watcher-32763-1149274317 -o ROOT/results/node68/solver-32763-1149274317 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user3/wildcat-skc ROOT/tmp/node68/32763-1149274317/instance-32763-1149274317.opb 962173404

MD5SUM SOLVER= e3d27fcb27e96c4c5fdaee74465b047d
MD5SUM BENCH=  0bd58fd61104d4efa74fac2638f06649

RANDOM SEED= 962173404


/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.279
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	: 5914.62
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.279
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:       1681888 kB
Buffers:         19820 kB
Cached:         290892 kB
SwapCached:       2292 kB
Active:          49220 kB
Inactive:       270080 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1681888 kB
SwapTotal:     4192956 kB
SwapFree:      4182316 kB
Dirty:             188 kB
Writeback:           0 kB
Mapped:          15580 kB
Slab:            40852 kB
Committed_AS:   249060 kB
PageTables:       1400 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node68 on Fri Jun  2 18:51:57 UTC 2006