Trace number 35580

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
minisat+ 1.14OPT2 0.000999 0.00503505

General information on the benchmark

Namenormalized-PB06/OPT-SMALLINT/submitted-PB05/
sorensson/garden/normalized-g2x2.opb
MD5SUMa698ae5e12697244f58af37f254243b4
Bench CategoryOPT-SMALLINT (optimisation, small integers)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark2
Best CPU time to get the best result obtained on this benchmark0.000999
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 2
Optimality of the best value was proved YES
Number of variables4
Total number of constraints4
Number of constraints which are clauses4
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints0
Minimum length of a constraint3
Maximum length of a constraint3
Number of terms in the objective function 4
Biggest coefficient in the objective function 1
Number of bits for the biggest coefficient in the objective function 1
Sum of the numbers in the objective function 4
Number of bits of the sum of numbers in the objective function 3
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 4
Number of bits of the biggest sum of numbers3
Number of products (including duplicates)0
Sum of products size (including duplicates)0
Number of different products0
Sum of products size0

Solver Data (download as text)

0.00	c Parsing PB file...
0.00	c Converting 4 PB-constraints to clauses...
0.00	c   -- Unit propagations: (none)
0.00	c   -- Detecting intervals from adjacent constraints: (none)
0.00	c   -- Clauses(.)/Splits(s): ....
0.00	c ==================================[MINISAT+]==================================
0.00	c | Conflicts | Original         | Learnt                           | Progress |
0.00	c |           | Clauses Literals |     Max Clauses Literals     LPC |          |
0.00	c ==============================================================================
0.00	c |         0 |       4       12 |       1       0        0     nan |  0.000 % |
0.00	c ==============================================================================
0.00	c Found solution: 2
0.00	o 2
0.00	c ---[   0]---> BDD-cost:    5
0.00	c ==================================[MINISAT+]==================================
0.00	c | Conflicts | Original         | Learnt                           | Progress |
0.00	c |           | Clauses Literals |     Max Clauses Literals     LPC |          |
0.00	c ==============================================================================
0.00	c |         0 |      15       41 |       5       0        0     nan |  0.000 % |
0.00	c ==============================================================================
0.00	c Optimal solution: 2
0.00	s OPTIMUM FOUND
0.00	v -x1 x2 x3 -x4
0.00	c _______________________________________________________________________________
0.00	c 
0.00	c restarts              : 2
0.00	c conflicts             : 3              (3003 /sec)
0.00	c decisions             : 5              (5005 /sec)
0.00	c propagations          : 0              (0 /sec)
0.00	c inspects              : 0              (0 /sec)
0.00	c CPU time              : 0.000999 s
0.00	c _______________________________________________________________________________

Verifier Data (download as text)

OK	2

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/node84/watcher-35580-1149286058 -o ROOT/results/node84/solver-35580-1149286058 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user7/minisat+ ROOT/tmp/node84/35580-1149286058/instance-35580-1149286058.opb 

Current StackSize limit: 67108864 bytes

!!! unable to read /proc/19487/task filesystem (No such file or directory) !!!/proc/loadavg: 0.57 0.86 0.88 2/67 19487
/proc/meminfo: memFree=1503776/2055892 swapFree=4085292/4096564
[pid=19487] ppid=19485 vsize=0 CPUtime=0
/proc/19487/stat : 19487 (minisat+) Z 19485 19487 19441 0 -1 4194316 136 0 0 0 0 0 0 0 20 0 1 0 194245104 0 0 18446744073709551615 0 0 0 0 0 0 0 4096 16386 18446744071563353775 0 0 17 1 0 0
/proc/19487/statm: 0 0 0 0 0 0 0

Child status: 30
Real time (s): 0.00503505
CPU time (s): 0.000999
CPU user time (s): 0.000999
CPU system time (s): 0
CPU usage (%): 19.8409
Max. virtual memory (cumulated for all children) (Kb): 0

Launcher Data (download as text)

Begin job on node84 on Fri Jun  2 22:07:38 UTC 2006


FILE ID= 35580-1149286058

PBS_JOBID= 306593

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-SMALLINT/submitted-PB05/sorensson/garden/normalized-g2x2.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user7/minisat+ ROOT/tmp/node84/35580-1149286058/instance-35580-1149286058.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node84/watcher-35580-1149286058 -o ROOT/results/node84/solver-35580-1149286058 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user7/minisat+ ROOT/tmp/node84/35580-1149286058/instance-35580-1149286058.opb

MD5SUM SOLVER= 490d1d4b9bbf010afe7f0af63a5a62db
MD5SUM BENCH=  a698ae5e12697244f58af37f254243b4

RANDOM SEED= 606211524


/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.231
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	: 6006.15
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.231
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	: 5999.43
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055892 kB
MemFree:       1503984 kB
Buffers:         30540 kB
Cached:         450080 kB
SwapCached:       2520 kB
Active:         124516 kB
Inactive:       364824 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055892 kB
LowFree:       1503984 kB
SwapTotal:     4096564 kB
SwapFree:      4085292 kB
Dirty:             284 kB
Writeback:           0 kB
Mapped:          16424 kB
Slab:            49248 kB
Committed_AS:   343224 kB
PageTables:       1272 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node84 on Fri Jun  2 22:07:38 UTC 2006