Trace number 1627001

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. The first timestamp (if present) is estimated CPU time. The last timestamp is wall clock 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
SAT07 reference solver: March KS 2007-02-08SAT 0.045992 0.0463521

General information on the benchmark

NameRANDOM/MEDIUM/3SAT/SATISFIABLE/380/
unif-k3-r4.25-v380-c1615-S1985172968-100.cnf
MD5SUMd341022d95ddbcad449a00c47578e9f1
Bench CategoryRANDOM (random instances)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.026995
Satisfiable
(Un)Satisfiability was proved
Number of variables380
Number of clauses1615
Sum of the clauses size4845
Maximum clause length3
Minimum clause length3
Number of clauses of size 10
Number of clauses of size 20
Number of clauses of size 31615
Number of clauses of size 40
Number of clauses of size 50
Number of clauses of size over 50

Solver Data 

0.00/0.01	c main():: ***                                   [ march satisfiability solver ]                                   ***
0.00/0.01	c main()::  **            Copyright (C) 2001-2004 M. Dufour, M. Heule, J. van Zwieten and H. van Maaren            **
0.00/0.01	c main()::   * This program may be redistributed and/or modified under the terms of the GNU Gereral Public License *
0.00/0.01	c main()::
0.00/0.01	c initFormula():: searching for DIMACS p-line....
0.00/0.01	c initFormula():: the DIMACS p-line indicates a CNF of 380 variables and 1615 clauses.
0.00/0.01	c parseCNF():: parsing....
0.00/0.01	c parseCNF():: the CNF contains 0 unary clauses.
0.00/0.01	c runParser():: parsing was successful, warming up engines...
0.00/0.01	c simplify_formula():: removed 0 tautological, 25 satisfied and 0 duplicate clauses
0.00/0.01	c preprocessing fase I completed:: there are now 377 free variables and 1590 clauses.
0.00/0.01	c stat :: sign balance is biased by 0.469
0.00/0.01	c shorten_equivalence(): average equivalence length reduced from nan to nan
0.00/0.01	c using 3-SAT heuristics (occurence based diff)
0.00/0.01	c longest clause has size 3
0.00/0.01	c simplify_formula():: removed 0 tautological, 0 satisfied and 177 duplicate clauses
0.00/0.01	c resolvent_look() :: found 89 resolvents
0.00/0.01	c lessRedundantTransformation():: nothing to be done.
0.00/0.01	c transformTo3SAT():: you gave me 380 variables and 1679 clauses.
0.00/0.01	c transformTo3SAT():: by the way, the maximal clause length before transformation was 3.
0.00/0.01	c transformTo3SAT():: I will add 0 variables and 0 clauses!
0.00/0.01	c transformTo3SAT():: the transformation yielded 380 variabels and 1679 clauses.
0.00/0.01	c main():: clause / variable ratio: ( 1679 / 380 ) = 4.42
0.00/0.01	c longest clause has size 3
0.00/0.01	c simplify_formula():: removed 0 tautological, 0 satisfied and 0 duplicate clauses
0.00/0.01	c dynamic_preselect_setsize :: off
0.00/0.01	c suggested doublelook initial :: 0
0.00/0.01	c main():: all systems go!
0.00/0.01	c |----------------------------------------------------------------|
0.00/0.04	c solution bin :: .00000000000000000001000000000000
0.00/0.04	c direction branchin :: current_rights = 1
0.00/0.04	
c |
0.00/0.04	c
0.00/0.04	c main():: nodeCount: 121
0.00/0.04	c main():: dead ends in main: 5
0.00/0.04	c main():: lookAheadCount: 6825
0.00/0.04	c main():: unitResolveCount: 1523
0.00/0.04	c main():: time=0.040000
0.00/0.04	c main():: necessary_assignments: 23
0.00/0.04	c main():: bin_sat: 0, bin_unsat 0
0.00/0.04	c main():: doublelook: #: 301, succes #: 187
0.00/0.04	c main():: doublelook: overall 4.537 of all possible doublelooks executed
0.00/0.04	c main():: doublelook: succesrate: 62.126, average DL_trigger: 5178.850
0.00/0.04	c main():: SOLUTION VERIFIED :-)
0.00/0.04	s SATISFIABLE
0.00/0.04	v 1 -2 -3 -4 -5 6 -7 -8 -9 10 11 12 -13 -14 15 -16 17 18 19 20 21 22 -23 24 -25 26 -27 28 -29 30 -31 32 33 34 35 36 37 38 39 -40 41 42 -43 -44 45 -46 47 -48 49 50 -51 52 53 54 -55 -56 -57 58 59 -60 61 -62 63 64 65 66 67 68 -69 70 71 72 -73 -74 75 -76 77 78 79 -80 81 82 83 -84 -85 -86 -87 88 -89 90 -91 92 -93 94 95 -96 -97 98 -99 100 101 -102 103 104 105 106 -107 -108 109 110 -111 112 -113 114 -115 116 117 118 -119 -120 -121 122 123 -124 125 126 -127 -128 -129 130 -131 132 133 -134 135 136 -137 -138 139 140 -141 -142 -143 144 145 -146 -147 -148 149 -150 151 -152 153 -154 -155 156 -157 158 -159 -160 161 -162 163 164 165 -166 167 168 -169 -170 171 -172 -173 174 175 -176 -177 178 179 180 -181 182 183 184 -185 -186 -187 -188 189 190 -191 192 -193 194 195 -196 -197 198 199 -200 -201 202 -203 204 205 206 -207 208 -209 -210 211 -212 213 214 215 216 217 218 219 -220 221 -222 -223 224 225 226 -227 228 229 230 -231 232 -233 234 -235 236 -237 -238 -239 -240 -241 -242 243 244 -245 246 247 -248 -249 -250 -251 -252 253 -254 255 256 257 258 -259 260 261 262 263 -264 265 266 267 -268 269 -270 -271 272 273 -274 -275 276 277 -278 279 280 281 -282 283 284 285 -286 -287 -288 -289 290 -291 292 -293 -294 -295 -296 297 -298 299 -300 301 302 -303 304 305 306 307 -308 -309 310 311 312 -313 -314 -315 -316 317 -318 319 -320 321 -322 -323 324 -325 326 -327 -328 329 330 331 -332 333 334 -335 336 -337 338 -339 340 -341 342 343 -344 345 -346 347 348 -349 350 -351 352 -353 -354 -355 -356 357 -358 -359 360 -361 362 363 -364 365 366 -367 368 369 370 371 372 373 374 375 376 377 378 -379 -380 0

Verifier Data 

OK

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-1627001-1240142340/watcher-1627001-1240142340 -o /tmp/evaluation-result-1627001-1240142340/solver-1627001-1240142340 -C 5000 -W 6000 -M 1800 --output-limit 1,15 HOME/march_ks HOME/instance-1627001-1240142340.cnf 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 5000 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 5030 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 6000 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 1843200 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 1894400 KiB
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 0.89 0.97 0.99 2/64 24929
/proc/meminfo: memFree=1243304/2055920 swapFree=4192956/4192956
[pid=24929] ppid=24927 vsize=792 CPUtime=0
/proc/24929/stat : 24929 (march_ks) R 24927 24929 24622 0 -1 4194304 122 0 0 0 0 0 0 0 18 0 1 0 42267476 811008 105 1992294400 134512640 135019032 4294956240 18446744073709551615 134554592 0 0 4096 0 0 0 0 17 0 0 0
/proc/24929/statm: 198 105 52 123 0 73 0

Solver just ended. Dumping a history of the last processes samples

Child status: 10
Real time (s): 0.0463521
CPU time (s): 0.045992
CPU user time (s): 0.044993
CPU system time (s): 0.000999
CPU usage (%): 99.2232
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.044993
system time used= 0.000999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 235
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= 2
involuntary context switches= 0

runsolver used 0.005999 second user time and 0.003999 second system time

The end

Launcher Data 

Begin job on node24 at 2009-04-19 13:59:00
IDJOB=1627001
IDBENCH=70735
IDSOLVER=582
FILE ID=node24/1627001-1240142340
PBS_JOBID= 9159270
Free space on /tmp= 66412 MiB

SOLVER NAME= SAT07 reference solver: March KS 2007-02-08
BENCH NAME= SAT09/RANDOM/MEDIUM/3SAT/SATISFIABLE/380/unif-k3-r4.25-v380-c1615-S1985172968-100.cnf
COMMAND LINE= HOME/march_ks BENCHNAME            
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1627001-1240142340/watcher-1627001-1240142340 -o /tmp/evaluation-result-1627001-1240142340/solver-1627001-1240142340 -C 5000 -W 6000 -M 1800 --output-limit 1,15  HOME/march_ks HOME/instance-1627001-1240142340.cnf            

TIME LIMIT= 5000 seconds
MEMORY LIMIT= 1800 MiB
MAX NB THREAD= 0

MD5SUM BENCH= d341022d95ddbcad449a00c47578e9f1
RANDOM SEED=708583243

node24.alineos.net Linux 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005

/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.232
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.232
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:       1243848 kB
Buffers:         94588 kB
Cached:         617236 kB
SwapCached:          0 kB
Active:         307216 kB
Inactive:       418936 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1243848 kB
SwapTotal:     4192956 kB
SwapFree:      4192956 kB
Dirty:            3128 kB
Writeback:           0 kB
Mapped:          24116 kB
Slab:            71896 kB
Committed_AS:   168252 kB
PageTables:       1440 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= 66408 MiB
End job on node24 at 2009-04-19 13:59:00