Trace number 1879704

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 NameAnswerobjCPU timeWall clock time
bsolo 3.1 pbOPT-4 0.007997 0.00836506

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-NLC/submittedPB07/
manquinho/bsg/normalized-bsg_10_4_4.opb
MD5SUMdb21482260ff555b3e36165a161b21f2
Bench CategoryOPT-SMALLINT-NLC (optimisation, small integers, non linear constraints)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark-4
Best CPU time to get the best result obtained on this benchmark0.012997
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function -4
Optimality of the best value was proved YES
Number of variables20
Total number of constraints31
Number of constraints which are clauses10
Number of constraints which are cardinality constraints (but not clauses)0
Number of constraints which are nor clauses,nor cardinality constraints21
Minimum length of a constraint2
Maximum length of a constraint20
Number of terms in the objective function 10
Biggest coefficient in the objective function 1
Number of bits for the biggest coefficient in the objective function 1
Sum of the numbers in the objective function 10
Number of bits of the sum of numbers in the objective function 4
Biggest number in a constraint 1
Number of bits of the biggest number in a constraint 1
Biggest sum of numbers in a constraint 20
Number of bits of the biggest sum of numbers5
Number of products (including duplicates)92
Sum of products size (including duplicates)184
Number of different products46
Sum of products size92

Quality of the solution as a function of time


Download the above graph as a PDF file / as an EPS file

Solver Data

0.00/0.00	c bsolo beta version 3.1 - 13/04/2009 : 1630 GMT
0.00/0.00	c Developed by Vasco Manquinho and José Santos IST/UTL - INESC-ID
0.00/0.00	c type "bsolo -h" for help
0.00/0.00	c Time Limit set via environment variable PBTIMEOUT to 1800
0.00/0.00	c Learning Strategy: Generic Pseudo-Boolean Learning
0.00/0.00	c Time Limit set to 1800
0.00/0.00	c Memory Limit set to 1800 MB
0.00/0.00	c Instance file HOME/instance-1879704-1245247267.opb
0.00/0.00	c File size is 4000 bytes.
0.00/0.00	c Highest Coefficient sum: 20
0.00/0.00	c Parsing was ok!!
0.00/0.00	c Total parsing time: 0 s
0.00/0.00	c Var: 66 Constr: 124 56/22/46 Lit: 428 Watch. Lit: 364
0.00/0.00	c Obj. Vars: 10 (15.1515 % of total variables)
0.00/0.00	c Pre-processing Time: 0.002 s
0.00/0.00	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.00	c        0     66      124      428    3      364     542      0      0 0.00
0.00/0.00	c Switching off lower bounding mode.
0.00/0.00	o -1
0.00/0.00	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.00	c        0     66      125      438    3      367     549      1      0 0.00
0.00/0.00	o -2
0.00/0.00	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.00	c        1     66      128      468    3      376     552      4    500 0.00
0.00/0.00	o -3
0.00/0.00	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.00	c       10     66      147      637    4      446     555     23   5000 0.00
0.00/0.00	o -4
0.00/0.00	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.00	c       38     59      204     1059    5      678     557     80   9500 0.00
0.00/0.00	v -x1 -x2 x3 -x4 x5 -x6 x7 -x8 x9 -x10 -x21 -x22 -x23 -x24 -x25 -x26 -x27 -x28 -x29 -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 -x57 -x58 -x59 -x60 -x61 x62 -x63 -x64 -x65 x66 -x11 x12 -x13 -x14 -x15 x16 -x17 x18 -x19 x20 
0.00/0.00	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
0.00/0.00	c    4       70     12      135      268     1568    144  11666 0.01
0.00/0.00	c Objective: -4
0.00/0.00	s OPTIMUM FOUND
0.00/0.00	c Total time: 0.006 s

Verifier Data

OK	-4

Watcher Data

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-1879704-1245247267/watcher-1879704-1245247267 -o /tmp/evaluation-result-1879704-1245247267/solver-1879704-1245247267 -C 1800 -W 2000 -M 1800 bsolo -l3 -t1800 -m1800 HOME/instance-1879704-1245247267.opb 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 2000 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
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 1.00 1.00 0.92 3/64 12252
/proc/meminfo: memFree=1747824/2055920 swapFree=4191900/4192956
[pid=12252] ppid=12250 vsize=18388 CPUtime=0
/proc/12252/stat : 12252 (bsolo) R 12250 12252 11807 0 -1 4194304 260 0 0 0 0 0 0 0 18 0 1 0 77459690 18829312 243 1992294400 134512640 137136520 4294956256 18446744073709551615 136568305 0 0 4096 16384 0 0 0 17 0 0 0
/proc/12252/statm: 4597 243 197 640 0 3953 0

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

Child status: 0
Real time (s): 0.00836506
CPU time (s): 0.007997
CPU user time (s): 0.006998
CPU system time (s): 0.000999
CPU usage (%): 95.6001
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.006998
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= 268
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.002999 second user time and 0.005999 second system time

The end

Launcher Data

Begin job on node33 at 2009-06-17 16:01:07
IDJOB=1879704
IDBENCH=48254
IDSOLVER=701
FILE ID=node33/1879704-1245247267
PBS_JOBID= 9372305
Free space on /tmp= 65952 MiB

SOLVER NAME= bsolo 3.1 pb
BENCH NAME= PB07/normalized-PB07/OPT-SMALLINT-NLC/submittedPB07/manquinho/bsg/normalized-bsg_10_4_4.opb
COMMAND LINE= bsolo -l3 -tTIMEOUT -mMEMLIMIT BENCHNAME
CONVERSION SCRIPT= PBconversionToLinear BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1879704-1245247267/watcher-1879704-1245247267 -o /tmp/evaluation-result-1879704-1245247267/solver-1879704-1245247267 -C 1800 -W 2000 -M 1800  bsolo -l3 -t1800 -m1800 HOME/instance-1879704-1245247267.opb

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

MD5SUM BENCH= db21482260ff555b3e36165a161b21f2
RANDOM SEED=1637899097

node33.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.261
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.261
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:       1748368 kB
Buffers:         65160 kB
Cached:         157972 kB
SwapCached:        384 kB
Active:         108312 kB
Inactive:       128180 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1748368 kB
SwapTotal:     4192956 kB
SwapFree:      4191900 kB
Dirty:            4060 kB
Writeback:           0 kB
Mapped:          21808 kB
Slab:            57068 kB
Committed_AS:   155236 kB
PageTables:       1392 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

CONVERSION COMMAND LINE= PBconversionToLinear HOME/instance-1879704-1245247267.opb

Free space on /tmp at the end= 65948 MiB
End job on node33 at 2009-06-17 16:01:07