Trace number 35931

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
minisat+ 1.14SAT 9.01263 9.02598

General information on the benchmark

Namenormalized-PB06/SATUNSAT-MEDINT/submitted-PB06/
manquiho/Aardal_1/normalized-cuww1.opb
MD5SUM52b3cfe13fa99e74b3b63fc245437649
Bench CategorySATUNSAT-MEDINT (no optimisation, medium 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.278957
Has Objective FunctionNO
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved NO
Number of variables60
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 constraint60
Maximum length of a constraint60
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 89643482
Number of bits of the biggest number in a constraint 27
Biggest sum of numbers in a constraint 740339225
Number of bits of the biggest sum of numbers30
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.01	c Converting 2 PB-constraints to clauses...
0.01	c   -- Unit propagations: (none)
0.01	c   -- Detecting intervals from adjacent constraints: #
0.01	c   -- Clauses(.)/Splits(s): (none)
0.01	c ---[   0]---> BDD-cost:   59
9.01	c ==================================[MINISAT+]==================================
9.01	c | Conflicts | Original         | Learnt                           | Progress |
9.01	c |           | Clauses Literals |     Max Clauses Literals     LPC |          |
9.01	c ==============================================================================
9.01	c |         0 |       0        0 |       0       0        0     nan |  0.000 % |
9.01	c ==============================================================================
9.01	c SATISFIABLE: No goal function specified.
9.01	s SATISFIABLE
9.01	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
9.01	v -x31 -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
9.01	v -x57 -x58 -x59 -x60
9.01	c _______________________________________________________________________________
9.01	c 
9.01	c restarts              : 1
9.01	c conflicts             : 0              (0 /sec)
9.01	c decisions             : 1              (0 /sec)
9.01	c propagations          : 0              (0 /sec)
9.01	c inspects              : 0              (0 /sec)
9.01	c CPU time              : 8.91264 s
9.01	c _______________________________________________________________________________

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

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.85 0.95 0.98 2/64 4717
/proc/meminfo: memFree=1521032/2055920 swapFree=4181372/4192956
[pid=4717] ppid=4715 vsize=1048 CPUtime=0
/proc/4717/stat : 4717 (minisat+) D 4715 4717 4671 0 -1 4194304 85 0 0 0 0 0 0 0 18 0 1 0 197702256 1073152 70 18446744073709551615 134512640 135395479 4294956688 18446744073709551615 135031051 0 2147483391 4096 16386 18446744072099781622 0 0 17 1 0 0
/proc/4717/statm: 262 70 58 215 0 44 0

Child status: 10
Real time (s): 9.02598
CPU time (s): 9.01263
CPU user time (s): 8.91264
CPU system time (s): 0.099984
CPU usage (%): 99.8521
Max. virtual memory (cumulated for all children) (Kb): 0

Launcher Data (download as text)

Begin job on node1 on Sat Jun  3 07:40:07 UTC 2006


FILE ID= 35931-1149320407

PBS_JOBID= 308602

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/SATUNSAT-MEDINT/submitted-PB06/manquiho/Aardal_1/normalized-cuww1.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user7/minisat+ ROOT/tmp/node1/35931-1149320407/instance-35931-1149320407.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node1/watcher-35931-1149320407 -o ROOT/results/node1/solver-35931-1149320407 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user7/minisat+ ROOT/tmp/node1/35931-1149320407/instance-35931-1149320407.opb

MD5SUM SOLVER= 490d1d4b9bbf010afe7f0af63a5a62db
MD5SUM BENCH=  52b3cfe13fa99e74b3b63fc245437649

RANDOM SEED= 432041554


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


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1521240 kB
Buffers:         27348 kB
Cached:         439404 kB
SwapCached:       3332 kB
Active:          32880 kB
Inactive:       442680 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1521240 kB
SwapTotal:     4192956 kB
SwapFree:      4181372 kB
Dirty:             360 kB
Writeback:           0 kB
Mapped:          14908 kB
Slab:            45116 kB
Committed_AS:   292720 kB
PageTables:       1468 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB


End job on node1 on Sat Jun  3 07:40:16 UTC 2006