Trace number 365592

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 NameAnswerObjective functionCPU timeWall clock time
oree 0.1.2 alphaUNSAT 0.357944 0.359428

General information on the benchmark

Namenormalized-PB06/OPT-BIGINT/mps-v2-20-10/ftp.netlib.org/
lp/data/normalized-mps-v2-20-10-scfxm1.opb
MD5SUMb00fcca5c7683bc6e417430bf4fc75bf
Bench CategoryOPT-BIGINT (optimisation, big integers)
Best result obtained on this benchmarkUNSAT
Best value of the objective obtained on this benchmark
Best CPU time to get the best result obtained on this benchmark0.214966
Has Objective FunctionYES
SatisfiableNO
(Un)Satisfiability was provedYES
Best value of the objective function
Optimality of the best value was proved
Number of variables13710
Total number of constraints327
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 constraints327
Minimum length of a constraint30
Maximum length of a constraint1710
Number of terms in the objective function 690
Biggest coefficient in the objective function 5368709120
Number of bits for the biggest coefficient in the objective function 33
Sum of the numbers in the objective function 140660178813
Number of bits of the sum of numbers in the objective function 38
Biggest number in a constraint 53687091200000
Number of bits of the biggest number in a constraint 46
Biggest sum of numbers in a constraint 326830904793855
Number of bits of the biggest sum of numbers49
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/0.00	c This is oree version 0.1.2 alpha
0.00/0.00	c (c) roussel@cril.univ-artois.fr
0.00/0.00	c using __gmp_expr<__gmpz_value, __gmpz_value>
0.00/0.00	c parsing...
0.19/0.27	c ...done
0.19/0.27	c #vars=13710 #constraints=515 hasObjective=yes
0.29/0.33	c res. mode=mod
0.29/0.33	c VSIDS like heuristics
0.29/0.33	c complete search running
0.29/0.35	c contradiction after root unit propagation
0.29/0.35	
0.29/0.35	s UNSATISFIABLE
0.29/0.35	
0.29/0.35	c user time= 0.341948 s
0.29/0.35	c system time= 0.011998 s
0.29/0.35	c wall clock time=0.353289

Verifier Data (download as text)

ERROR: no interpretation found !

Watcher Data (download as text)

runsolver version 3.2.2 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node5/watcher-365592-1176995255 -o ROOT/results/node5/solver-365592-1176995255 -C 1800 -W 3600 -M 1800 --output-limit 1,15 oree /tmp/evaluation/365592-1176995255/instance-365592-1176995255.opb mod 

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): 3600 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
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 0.99 0.97 0.96 3/77 32207
/proc/meminfo: memFree=1702720/2055920 swapFree=4151632/4192956
[pid=32207] ppid=32205 vsize=1468 CPUtime=0
/proc/32207/stat : 32207 (oree) R 32205 32207 31536 0 -1 4194304 181 0 0 0 0 0 0 0 18 0 1 0 175563134 1503232 163 18446744073709551615 134512640 135812674 4294956704 18446744073709551615 134546592 0 0 4096 17474 0 0 0 17 1 0 0
/proc/32207/statm: 367 163 131 317 0 46 0

[startup+0.0707821 s]
/proc/loadavg: 0.99 0.97 0.96 3/77 32207
/proc/meminfo: memFree=1702720/2055920 swapFree=4151632/4192956
[pid=32207] ppid=32205 vsize=2668 CPUtime=0.06
/proc/32207/stat : 32207 (oree) R 32205 32207 31536 0 -1 4194304 463 0 0 0 6 0 0 0 18 0 1 0 175563134 2732032 445 18446744073709551615 134512640 135812674 4294956704 18446744073709551615 135274709 0 0 4096 17474 0 0 0 17 1 0 0
/proc/32207/statm: 667 445 131 317 0 346 0
Current children cumulated CPU time (s) 0.06
Current children cumulated vsize (KiB) 2668

[startup+0.101785 s]
/proc/loadavg: 0.99 0.97 0.96 3/77 32207
/proc/meminfo: memFree=1702720/2055920 swapFree=4151632/4192956
[pid=32207] ppid=32205 vsize=3200 CPUtime=0.09
/proc/32207/stat : 32207 (oree) R 32205 32207 31536 0 -1 4194304 603 0 0 0 9 0 0 0 18 0 1 0 175563134 3276800 585 18446744073709551615 134512640 135812674 4294956704 18446744073709551615 134760686 0 0 4096 17474 0 0 0 17 1 0 0
/proc/32207/statm: 800 585 131 317 0 479 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 3200

[startup+0.301807 s]
/proc/loadavg: 0.99 0.97 0.96 3/77 32207
/proc/meminfo: memFree=1702720/2055920 swapFree=4151632/4192956
[pid=32207] ppid=32205 vsize=7524 CPUtime=0.29
/proc/32207/stat : 32207 (oree) R 32205 32207 31536 0 -1 4194304 1693 0 0 0 28 1 0 0 19 0 1 0 175563134 7704576 1675 18446744073709551615 134512640 135812674 4294956704 18446744073709551615 135274709 0 0 4096 17474 0 0 0 17 1 0 0
/proc/32207/statm: 1881 1675 137 317 0 1560 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 7524

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

Child status: 0
Real time (s): 0.359428
CPU time (s): 0.357944
CPU user time (s): 0.343947
CPU system time (s): 0.013997
CPU usage (%): 99.5871
Max. virtual memory (cumulated for all children) (KiB): 7524

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.343947
system time used= 0.013997
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1956
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= 8
involuntary context switches= 2

runsolver used 0.002999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node5 on Thu Apr 19 15:07:35 UTC 2007

IDJOB= 365592
IDBENCH= 2444
IDSOLVER= 172
FILE ID= node5/365592-1176995255

PBS_JOBID= 4630432

Free space on /tmp= 66355 MiB

SOLVER NAME= oree 0.1.2 alpha
BENCH NAME= HOME/pub/bench/PB06//final/normalized-PB06/OPT-BIGINT/mps-v2-20-10/ftp.netlib.org/lp/data/normalized-mps-v2-20-10-scfxm1.opb
COMMAND LINE= oree /tmp/evaluation/365592-1176995255/instance-365592-1176995255.opb mod           
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node5/watcher-365592-1176995255 -o ROOT/results/node5/solver-365592-1176995255 -C 1800 -W 3600 -M 1800 --output-limit 1,15  oree /tmp/evaluation/365592-1176995255/instance-365592-1176995255.opb mod           

META MD5SUM SOLVER= 4e41df0f0543e325f03c5155f85b9e9b
MD5SUM BENCH=  b00fcca5c7683bc6e417430bf4fc75bf

RANDOM SEED= 3637055

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 1800 MiB

Linux node5.alineos.net 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005 x86_64 x86_64 x86_64 GNU/Linux

/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.232
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.232
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:       1703128 kB
Buffers:         31808 kB
Cached:         257440 kB
SwapCached:       9408 kB
Active:          61016 kB
Inactive:       251196 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1703128 kB
SwapTotal:     4192956 kB
SwapFree:      4151632 kB
Dirty:            2484 kB
Writeback:           0 kB
Mapped:          29940 kB
Slab:            26188 kB
Committed_AS:  8663848 kB
PageTables:       1720 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66355 MiB

End job on node5 on Thu Apr 19 15:07:35 UTC 2007