Trace number 44923

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 1.25581 1.2579

General information on the benchmark

Namenormalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/namasivayam/
wnqueen/normalized-t2001.13queen13.1110973478.opb
MD5SUM1c338f912c482d8eb76221229960cff3
Bench CategorySATUNSAT-SMALLINT (no optimisation, small integers)
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.024995
Has Objective FunctionNO
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved NO
Number of variables169
Total number of constraints101
Number of constraints which are clauses30
Number of constraints which are cardinality constraints (but not clauses)70
Number of constraints which are nor clauses,nor cardinality constraints1
Minimum length of a constraint2
Maximum length of a constraint169
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 38
Number of bits of the biggest number in a constraint 6
Biggest sum of numbers in a constraint 1193
Number of bits of the biggest sum of numbers11
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
1.25	s SATISFIABLE
1.25	v x10 x14 x32 x41 x61 x76 x86 x96 x107 x129 x137 x147 x169 -x1 -x2 -x3 -x4 -x5 -x6 -x7 -x8 -x9 -x11 -x12 -x13 -x15 -x16 -x17 -x18 -x19
1.25	v -x20 -x21 -x22 -x23 -x24 -x25 -x26 -x27 -x28 -x29 -x30 -x31 -x33 -x34 -x35 -x36 -x37 -x38 -x39 -x40 -x42 -x43 -x44 -x45 -x46 -x47
1.25	v -x48 -x49 -x50 -x51 -x52 -x53 -x54 -x55 -x56 -x57 -x58 -x59 -x60 -x62 -x63 -x64 -x65 -x66 -x67 -x68 -x69 -x70 -x71 -x72 -x73 -x74
1.25	v -x75 -x77 -x78 -x79 -x80 -x81 -x82 -x83 -x84 -x85 -x87 -x88 -x89 -x90 -x91 -x92 -x93 -x94 -x95 -x97 -x98 -x99 -x100 -x101 -x102
1.25	v -x103 -x104 -x105 -x106 -x108 -x109 -x110 -x111 -x112 -x113 -x114 -x115 -x116 -x117 -x118 -x119 -x120 -x121 -x122 -x123 -x124
1.25	v -x125 -x126 -x127 -x128 -x130 -x131 -x132 -x133 -x134 -x135 -x136 -x138 -x139 -x140 -x141 -x142 -x143 -x144 -x145 -x146 -x148
1.25	v -x149 -x150 -x151 -x152 -x153 -x154 -x155 -x156 -x157 -x158 -x159 -x160 -x161 -x162 -x163 -x164 -x165 -x166 -x167 -x168

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/node67/watcher-44923-1149641335 -o ROOT/results/node67/solver-44923-1149641335 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user4/pbsmodels-v1.31/runpbsmodels ROOT/tmp/node67/44923-1149641335/instance-44923-1149641335.opb 113807583 ROOT/tmp/node67/44923-1149641335 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.33 0.76 0.85 2/64 22281
/proc/meminfo: memFree=1764784/2055920 swapFree=4181756/4192956
[pid=22281] ppid=22279 vsize=5360 CPUtime=0
/proc/22281/stat : 22281 (runpbsmodels) S 22279 22281 22235 0 -1 4194304 286 0 0 0 0 0 0 0 19 0 1 0 229802886 5488640 234 18446744073709551615 4194304 4889804 548682069184 18446744073709551615 271638389572 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/22281/statm: 1340 234 195 169 0 51 0
[pid=22282] ppid=22281 vsize=4708 CPUtime=0
/proc/22282/stat : 22282 (pbsmodels-v1.31) R 22281 22281 22235 0 -1 4194304 61 0 0 0 0 0 0 0 20 0 1 0 229802887 4820992 43 18446744073709551615 4194304 4206940 548682069024 18446744073709551615 271635772809 0 0 4096 0 0 0 0 17 1 0 0
/proc/22282/statm: 1567 47 36 3 0 8 0

Child status: 0
Real time (s): 1.2579
CPU time (s): 1.25581
CPU user time (s): 1.23981
CPU system time (s): 0.015997
CPU usage (%): 99.8338
Max. virtual memory (cumulated for all children) (Kb): 0
The end

Launcher Data (download as text)

Begin job on node67 on Wed Jun  7 00:48:55 UTC 2006


FILE ID= 44923-1149641335

PBS_JOBID= 323422

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/SATUNSAT-SMALLINT/submitted-PB06/namasivayam/wnqueen/normalized-t2001.13queen13.1110973478.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user4/pbsmodels-v1.31/runpbsmodels ROOT/tmp/node67/44923-1149641335/instance-44923-1149641335.opb 113807583  ROOT/tmp/node67/44923-1149641335
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node67/watcher-44923-1149641335 -o ROOT/results/node67/solver-44923-1149641335 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user4/pbsmodels-v1.31/runpbsmodels ROOT/tmp/node67/44923-1149641335/instance-44923-1149641335.opb 113807583  ROOT/tmp/node67/44923-1149641335

MD5SUM SOLVER= 95562bc622ddb1f976359072aec5ad24 7fcd858753252b26b88f3383e979819a c732bc4c3aeda9195daa74a308a1f78e b7e54d975d35ab28450b6de5c14d303e f7da3270b2cd5190fa0cd9af9b854ca4
MD5SUM BENCH=  1c338f912c482d8eb76221229960cff3

RANDOM SEED= 113807583


/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.264
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.264
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:       1764992 kB
Buffers:         27608 kB
Cached:         202280 kB
SwapCached:       2944 kB
Active:          74668 kB
Inactive:       164028 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1764992 kB
SwapTotal:     4192956 kB
SwapFree:      4181756 kB
Dirty:             280 kB
Writeback:           0 kB
Mapped:          14792 kB
Slab:            38252 kB
Committed_AS:   431012 kB
PageTables:       1472 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node67 on Wed Jun  7 00:48:56 UTC 2006