Trace number 40814

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
bsolo 2006/05SAT 5.2792 5.28905

General information on the benchmark

Namenormalized-PB06/SATUNSAT-MEDINT/submitted-PB06/
manquiho/Aardal_1/normalized-prob1.opb
MD5SUM3fa3d77c564aea49e42df3fe632e1a1c
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 benchmark5.2792
Has Objective FunctionNO
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved NO
Number of variables77
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 constraint77
Maximum length of a constraint77
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 33367336
Number of bits of the biggest number in a constraint 25
Biggest sum of numbers in a constraint 458257453
Number of bits of the biggest sum of numbers29
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 Time Limit set via PBTIMEOUT to 1800
0.01	c INFO: OSL Context initialized.
0.01	c BIG Int formula...
0.01	c Initial problem consists of 77 variables and 2 constraints.
0.01	c Using non-optimization problem switches.
0.01	c No problem reductions applied in OPT. instance.
0.01	c	preprocess terminated. Elapsed time: 0.008
0.01	c After prepocess the problem consists of 77 variables and 2 constraints.
0.02	c Restart #1 #Var: 77 LB: 0 @ 0.016
0.04	c Restart #2 #Var: 77 LB: 0 @ 0.034
0.08	c Restart #3 #Var: 77 LB: 0 @ 0.069
0.12	c Restart #4 #Var: 77 LB: 0 @ 0.116
0.17	c Restart #5 #Var: 77 LB: 0 @ 0.164
0.24	c Restart #6 #Var: 77 LB: 0 @ 0.23
0.32	c Restart #7 #Var: 77 LB: 0 @ 0.315
0.44	c Restart #8 #Var: 77 LB: 0 @ 0.432
0.55	c Restart #9 #Var: 77 LB: 0 @ 0.545
0.70	c Restart #10 #Var: 77 LB: 0 @ 0.691
0.84	c Restart #11 #Var: 77 LB: 0 @ 0.836
1.10	c Restart #12 #Var: 77 LB: 0 @ 1.091
1.41	c Restart #13 #Var: 77 LB: 0 @ 1.408
1.69	c Restart #14 #Var: 77 LB: 0 @ 1.686
2.00	c Restart #15 #Var: 77 LB: 0 @ 1.99
2.47	c Restart #16 #Var: 77 LB: 0 @ 2.464
3.02	c Restart #17 #Var: 77 LB: 0 @ 3.012
3.48	c Restart #18 #Var: 77 LB: 0 @ 3.472
4.09	c Restart #19 #Var: 77 LB: 0 @ 4.084
4.60	c Restart #20 #Var: 77 LB: 0 @ 4.592
5.27	c Sol. found (all assignments made)...
5.27	o 0
5.27	c NEW SOLUTION FOUND: 0 @ 5.266
5.27	s SATISFIABLE
5.27	c Cost: 0
5.27	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
5.27	v -x30 -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
5.27	v -x57 -x58 -x59 -x60 -x61 -x62 -x63 x64 -x65 -x66 -x67 -x68 -x69 -x70 -x71 -x72 -x73 -x74 -x75 -x76 -x77
5.27	c Exit Code: 10
5.27	c Total time: 5.267 s

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/node16/watcher-40814-1149320710 -o ROOT/results/node16/solver-40814-1149320710 -C 1800 -M 1800 -S 64 ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node16/40814-1149320710/instance-40814-1149320710.opb 

Current StackSize limit: 67108864 bytes

/proc/loadavg: 0.84 0.97 0.97 2/64 24972
/proc/meminfo: memFree=1844224/2055920 swapFree=4181468/4192956
[pid=24972] ppid=24970 vsize=4932 CPUtime=0
/proc/24972/stat : 24972 (bsolo) D 24970 24972 24926 0 -1 0 366 0 0 0 0 0 0 0 18 0 1 0 197733827 5050368 330 18446744073709551615 134512640 134738892 4294956688 18446744073709551615 4294960144 0 2147483391 4096 16384 18446744072099781622 0 0 17 1 0 0
/proc/24972/statm: 1233 330 226 55 0 125 0

Child status: 10
Real time (s): 5.28905
CPU time (s): 5.2792
CPU user time (s): 5.15921
CPU system time (s): 0.119981
CPU usage (%): 99.8138
Max. virtual memory (cumulated for all children) (Kb): 0

Launcher Data (download as text)

Begin job on node16 on Sat Jun  3 07:45:10 UTC 2006


FILE ID= 40814-1149320710

PBS_JOBID= 308631

BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/SATUNSAT-MEDINT/submitted-PB06/manquiho/Aardal_1/normalized-prob1.opb
COMMAND LINE= ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node16/40814-1149320710/instance-40814-1149320710.opb
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node16/watcher-40814-1149320710 -o ROOT/results/node16/solver-40814-1149320710 -C 1800 -M 1800 -S 64  ROOT/solvers/PB/PB06final/user10/bsolo ROOT/tmp/node16/40814-1149320710/instance-40814-1149320710.opb

MD5SUM SOLVER= 05cada221eb1efaaae980ebc7509e7e8
MD5SUM BENCH=  3fa3d77c564aea49e42df3fe632e1a1c

RANDOM SEED= 705182285


/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:       1844432 kB
Buffers:          7184 kB
Cached:         136428 kB
SwapCached:       2860 kB
Active:          29432 kB
Inactive:       122508 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1844432 kB
SwapTotal:     4192956 kB
SwapFree:      4181468 kB
Dirty:             184 kB
Writeback:           0 kB
Mapped:          14732 kB
Slab:            45576 kB
Committed_AS:   296124 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 node16 on Sat Jun  3 07:45:15 UTC 2006