Trace number 1876731

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.1OPT2 0.003998 0.00538495

General information on the benchmark

Namenormalized-PB07/OPT-SMALLINT-NLC/submittedPB07/
manquinho/mds/normalized-mds_10_4_1.opb
MD5SUMf70b84a36f03e8071c6ec1558786823a
Bench CategoryOPT-SMALLINT-NLC (optimisation, small integers, non linear constraints)
Best result obtained on this benchmarkOPT
Best value of the objective obtained on this benchmark2
Best CPU time to get the best result obtained on this benchmark0.002999
Has Objective FunctionYES
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function 2
Optimality of the best value was proved YES
Number of variables10
Total number of constraints10
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 constraints10
Minimum length of a constraint5
Maximum length of a constraint8
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 10
Number of bits of the biggest sum of numbers4
Number of products (including duplicates)48
Sum of products size (including duplicates)96
Number of different products48
Sum of products size96

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: Cardinality Constraint 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-1876731-1245193986.opb
0.00/0.00	c File size is 3320 bytes.
0.00/0.00	c Highest Coefficient sum: 10
0.00/0.00	c Parsing was ok!!
0.00/0.00	c Total parsing time: 0 s
0.00/0.00	c Var: 58 Constr: 106 58/0/48 Lit: 346 Watch. Lit: 260
0.00/0.00	c Obj. Vars: 10 (17.2414 % of total variables)
0.00/0.00	c Pre-processing Time: 0.001 s
0.00/0.00	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.00	c        0     58      106      346    3      260     307      0      0 0.00
0.00/0.00	c Switching off lower bounding mode.
0.00/0.00	o 9
0.00/0.00	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.00	c        0     58      107      356    3      263     313      1      0 0.00
0.00/0.00	o 8
0.00/0.00	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.00	c        0     58      108      366    3      267     323      2      0 0.00
0.00/0.00	o 6
0.00/0.00	c    Confl   Vars     Ctrs     Lits  LPC   W.Lits     Max Learnt Conf/s Time
0.00/0.00	c        1     58      110      384    3      275     330      4   1000 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        1     58      111      394    3      284     340      5   1000 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     58      112      404    3      294     343      6   1000 0.00
0.00/0.00	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 -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 
0.00/0.00	c  Rst    Confl    NCB      Dec     Ctrs     Lits Learnt Conf/s Time
0.00/0.00	c    5        6      2       75      117      430     11   6000 0.00
0.00/0.00	c Objective: 2
0.00/0.00	s OPTIMUM FOUND
0.00/0.00	c Total time: 0.001 s

Verifier Data 

OK	2

Watcher Data 

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-1876731-1245193986/watcher-1876731-1245193986 -o /tmp/evaluation-result-1876731-1245193986/solver-1876731-1245193986 -C 1800 -W 2000 -M 1800 bsolo -l2 -t1800 -m1800 HOME/instance-1876731-1245193986.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 1.00 3/64 9309
/proc/meminfo: memFree=1889432/2055920 swapFree=4191900/4192956
[pid=9309] ppid=9307 vsize=0 CPUtime=0
/proc/9309/stat : 9309 (bsolo) Z 9307 9309 8935 0 -1 4194316 258 0 0 0 0 0 0 0 18 0 1 0 72131550 0 0 1992294400 0 0 0 0 0 0 0 4096 16384 18446744071563351923 0 0 17 0 0 0
/proc/9309/statm: 0 0 0 0 0 0 0

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

Child status: 0
Real time (s): 0.00538495
CPU time (s): 0.003998
CPU user time (s): 0.000999
CPU system time (s): 0.002999
CPU usage (%): 74.2439
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.000999
system time used= 0.002999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 258
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.001999 second user time and 0.006998 second system time

The end

Launcher Data 

Begin job on node33 at 2009-06-17 01:13:06
IDJOB=1876731
IDBENCH=48141
IDSOLVER=699
FILE ID=node33/1876731-1245193986
PBS_JOBID= 9368299
Free space on /tmp= 65952 MiB

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

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

MD5SUM BENCH= f70b84a36f03e8071c6ec1558786823a
RANDOM SEED=687477418

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:       1889912 kB
Buffers:         42852 kB
Cached:          68148 kB
SwapCached:        384 kB
Active:          68572 kB
Inactive:        55820 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1889912 kB
SwapTotal:     4192956 kB
SwapFree:      4191900 kB
Dirty:            3944 kB
Writeback:           0 kB
Mapped:          21808 kB
Slab:            27628 kB
Committed_AS:   128420 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-1876731-1245193986.opb

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