Trace number 44828

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
PB-smodels 1.31SAT 0.032994 0.0301519

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/reduced/submitted-PB06/
manquiho/Aardal_1/normalized-reduced-prob4.opb
MD5SUM7a618cad7be8e40ee9b04d7e51e41331
Bench CategorySATUNSAT-SMALLINT-LIN (no optimisation, small integers, linear constraints)
Best result obtained on this benchmarkSAT
Best value of the objective obtained on this benchmark0
Best CPU time to get the best result obtained on this benchmark0.001998
Has Objective FunctionNO
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved NO
Number of variables82
Total number of constraints2
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 constraints2
Minimum length of a constraint82
Maximum length of a constraint82
Number of terms in the objective function 0
Biggest coefficient in the objective function 0
Number of bits for the biggest coefficient in the objective function 0
Sum of the numbers in the objective function 0
Number of bits of the sum of numbers in the objective function 0
Biggest number in a constraint 39638
Number of bits of the biggest number in a constraint 16
Biggest sum of numbers in a constraint 524328
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

Solver Data (download as text)

0.00	c Running pbsmodels-v1.31
0.02	s SATISFIABLE
0.02	v x1 x2 x5 x13 x16 x17 x23 x24 x27 x28 x35 x36 x43 x44 x55 x56 x61 x63 x64 x66 x69 x70 x73 x74 x76 x79 -x3 -x4 -x6 -x7 -x8 -x9 -x10 -x11
0.02	v -x12 -x14 -x15 -x18 -x19 -x20 -x21 -x22 -x25 -x26 -x29 -x30 -x31 -x32 -x33 -x34 -x37 -x38 -x39 -x40 -x41 -x42 -x45 -x46 -x47 -x48
0.02	v -x49 -x50 -x51 -x52 -x53 -x54 -x57 -x58 -x59 -x60 -x62 -x65 -x67 -x68 -x71 -x72 -x75 -x77 -x78 -x80 -x81 -x82

Verifier Data (download as text)

OK	0

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

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

Enforcing memory limit (will send SIGKILL): 1843200 Kb
Enforcing VSIZE limit: 1887436800 bytes
command line: runsolver --timestamp -w ROOT/results/node77/watcher-44828-1149641045 -o ROOT/results/node77/solver-44828-1149641045 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user4/pbsmodels-v1.31/runpbsmodels ROOT/tmp/node77/44828-1149641045/instance-44828-1149641045.opb 611097755 ROOT/tmp/node77/44828-1149641045 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.84 0.94 0.90 2/67 2444
/proc/meminfo: memFree=1683584/2055892 swapFree=4085328/4096564
[pid=2444] ppid=2442 vsize=5368 CPUtime=0
/proc/2444/stat : 2444 (runpbsmodels) S 2442 2444 2398 0 -1 4194304 285 0 0 0 0 0 0 0 19 0 1 0 229743731 5496832 233 18446744073709551615 4194304 4889804 548682069184 18446744073709551615 268242053700 0 65536 4100 65538 18446744071563358023 0 0 17 0 0 0
/proc/2444/statm: 1342 233 194 169 0 52 0
[pid=2445] ppid=2444 vsize=12136 CPUtime=0
/proc/2445/stat : 2445 (pbsmodels-v1.31) D 2444 2444 2398 0 -1 4194304 270 0 0 0 0 0 0 0 20 0 1 0 229743732 12427264 236 18446744073709551615 4194304 4206940 548682069024 18446744073709551615 268250954798 0 2147483391 4224 0 18446744072099917094 0 0 17 0 0 0
/proc/2445/statm: 3034 236 179 3 0 133 0

Child status: 0
Real time (s): 0.0301519
CPU time (s): 0.032994
CPU user time (s): 0.014997
CPU system time (s): 0.017997
CPU usage (%): 109.426
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node77 on Wed Jun  7 00:44:05 UTC 2006


FILE ID= 44828-1149641045

PBS_JOBID= 323327

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/SATUNSAT-SMALLINT/reduced/submitted-PB06/manquiho/Aardal_1/normalized-reduced-prob4.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user4/pbsmodels-v1.31/runpbsmodels ROOT/tmp/node77/44828-1149641045/instance-44828-1149641045.opb 611097755  ROOT/tmp/node77/44828-1149641045
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node77/watcher-44828-1149641045 -o ROOT/results/node77/solver-44828-1149641045 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user4/pbsmodels-v1.31/runpbsmodels ROOT/tmp/node77/44828-1149641045/instance-44828-1149641045.opb 611097755  ROOT/tmp/node77/44828-1149641045

MD5SUM SOLVER= 95562bc622ddb1f976359072aec5ad24 7fcd858753252b26b88f3383e979819a c732bc4c3aeda9195daa74a308a1f78e b7e54d975d35ab28450b6de5c14d303e f7da3270b2cd5190fa0cd9af9b854ca4
MD5SUM BENCH=  7a618cad7be8e40ee9b04d7e51e41331

RANDOM SEED= 611097755


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


/proc/meminfo:
MemTotal:      2055892 kB
MemFree:       1683792 kB
Buffers:         34716 kB
Cached:         267980 kB
SwapCached:       2488 kB
Active:          85624 kB
Inactive:       225848 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055892 kB
LowFree:       1683792 kB
SwapTotal:     4096564 kB
SwapFree:      4085328 kB
Dirty:             284 kB
Writeback:           0 kB
Mapped:          16132 kB
Slab:            47304 kB
Committed_AS:   443160 kB
PageTables:       1276 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node77 on Wed Jun  7 00:44:05 UTC 2006