Trace number 3496019

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
MinisatID 2.5.2-gmp (fixed)? (exit code) 0.000999 0.005906

General information on the benchmark

Namenormalized-PB07/SATUNSAT-SMALLINT-NLC/submittedPB07/
manquinho/dbsg/normalized-dbsg_50_25_4_5.opb
MD5SUMb59e33bacf4f8d5e91915df093d27c73
Bench CategoryDEC-SMALLINT-NLC (no optimisation, small integers, non linear constraints)
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.011997
Has Objective FunctionNO
SatisfiableYES
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved NO
Number of variables100
Total number of constraints152
Number of constraints which are clauses50
Number of constraints which are cardinality constraints (but not clauses)1
Number of constraints which are nor clauses,nor cardinality constraints101
Minimum length of a constraint2
Maximum length of a constraint100
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 5
Number of bits of the biggest number in a constraint 3
Biggest sum of numbers in a constraint 100
Number of bits of the biggest sum of numbers7
Number of products (including duplicates)2932
Sum of products size (including duplicates)5864
Number of different products1466
Sum of products size2932

Solver Data

0.00/0.00	Leaving out linearization of opb constraints is not supported!

Verifier Data

ERROR: no interpretation found !

Watcher Data

runsolver Copyright (C) 2010-2011 Olivier ROUSSEL

This is runsolver version 3.3.1 (svn: 989)

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-3496019-1307934189/watcher-3496019-1307934189 -o /tmp/evaluation-result-3496019-1307934189/solver-3496019-1307934189 -C 1800 -W 1900 -M 15500 HOME/minisatid-gmp HOME/instance-3496019-1307934189.opb --verbosity=0 --format=opb --randomseed=526585297 

running on 4 cores: 1,3,5,7

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): 1900 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 15872000 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 15923200 KiB
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 1.79 1.93 1.97 2/177 7910
/proc/meminfo: memFree=7711628/32951124 swapFree=67049472/67111528
[pid=7910] ppid=7908 vsize=0 CPUtime=0 cores=1,3,5,7
/proc/7910r limi: 7910 ()vSIZE lo)Tck 220767 --v1 420251163SIGIGIGIGIGIGIGIG25GIG1GIG9836E/in7GIGIG3355443GKILLLLLLLLLLLLLLLL4096 17571nd 446744073709551615LLLLL17 3LLLLLLores=1,3,5,7
/prm:LLLLLLLLLLLLLL

erdata"juof lver . Dump0 Kia svntver.ber of solvee runsowhicverer 

Childions supro
io CPtd>Be(setu"noresul
n">Be(setu"noresul
s and  trad>Be(setu"
s ansystemBe(setu"noresul
s and time(%etur6.915
"le.it is on the vir(cumutions check valuild320) (imietu"

getrd tim(RUSAGpm8#,Suild320) (imietu"

getrd tim(RUSAGpm8#,SuL):d>B20pin ca:
resul
s an als="

r6.915
"le.i als="
n the vimWatcher Dataa>
ThelassL>
runsolver auncherdata">LAUerdaBegsefjobng Cnode118tput run-06 -- 05:03:09
IDJOB=osity=0
IDBENCHSAT-SM
IDis theixed)
FILE ID=node118/osity=0 --format=o
RUNJOBID=Cnode118 --for19797s r786
PBS_JOBID=C17449661
910] spver in19-13=C18212 Mavg:is the NAME= a>
<
ed DOM SEEDes: 1,3,5,ofnode118.amp -os.n seLinuxd  6.18 -64.el5 #1 SMP Thuicep
erd3:28:355EDTt r09

fo which prov:
d>Be(seor	u"

ERCdor_id	u"re  preI/pil
ch tfamily	u"6
model		u"26
modeler Da	u"I/pil(R) Xeon(R) r(cuuuuuuuuuuuX5ins  @d  67GHz
.91per 
	u"5
ch tMHz		u"2666.842
cac in the	u"8192 KB
physicrkBe(seor	u"1
ERCdor_id	u"re  preI/pil
ch tfamily	u"6
model		u"26
modeler Da	u"I/pil(R) Xeon(R) r(cuuuuuuuuuuuX5ins  @d  67GHz
.91per 
	u"5
ch tMHz		u"2666.842
cac in the	u"8192 KB
physicrkBe(seor	u"2
ERCdor_id	u"re  preI/pil
ch tfamily	u"6
model		u"26
modeler Da	u"I/pil(R) Xeon(R) r(cuuuuuuuuuuuX5ins  @d  67GHz
.91per 
	u"5
ch tMHz		u"2666.842
cac in the	u"8192 KB
physicrkBe(seor	u"3
ERCdor_id	u"re  preI/pil
ch tfamily	u"6
model		u"26
modeler Da	u"I/pil(R) Xeon(R) r(cuuuuuuuuuuuX5ins  @d  67GHz
.91per 
	u"5
ch tMHz		u"2666.842
cac in the	u"8192 KB
physicrkBe(seor	u"4
ERCdor_id	u"re  preI/pil
ch tfamily	u"6
model		u"26
modeler Da	u"I/pil(R) Xeon(R) r(cuuuuuuuuuuuX5ins  @d  67GHz
.91per 
	u"5
ch tMHz		u"2666.842
cac in the	u"8192 KB
physicrkBe(seor	u"5
ERCdor_id	u"re  preI/pil
ch tfamily	u"6
model		u"26
modeler Da	u"I/pil(R) Xeon(R) r(cuuuuuuuuuuuX5ins  @d  67GHz
.91per 
	u"5
ch tMHz		u"2666.842
cac in the	u"8192 KB
physicrkBe(seor	u"6
ERCdor_id	u"re  preI/pil
ch tfamily	u"6
model		u"26
modeler Da	u"I/pil(R) Xeon(R) r(cuuuuuuuuuuuX5ins  @d  67GHz
.91per 
	u"5
ch tMHz		u"2666.842
cac in the	u"8192 KB
physicrkBe(seor	u"7
ERCdor_id	u"re  preI/pil
ch tfamily	u"6
model		u"26
modeler Da	u"I/pil(R) Xeon(R) r(cuuuuuuuuuuuX5ins  @d  67GHz
.91per 
	u"5
ch tMHz		u"2666.842
cac in the	u"8192 KB
physicrk/96019 <>PB'1>