details

property	value
status	complete
benchmark	rt1-5.xml
ran by	Akihisa Yamada
cpu timeout	1200 seconds
wallclock timeout	300 seconds
memory limit	137438953472 bytes
execution host	n041.star.cs.uiowa.edu
space	Relative_05

run statistics

property	value
solver	AProVE
configuration	standard
runtime (wallclock)	2.21033 seconds
cpu usage	5.39863
user time	5.14682
system time	0.251815
max virtual memory	5.5802152E7
max residence set size	475472.0

stage attributes

key	value
starexec-result	YES

output

5.12/2.15 YES 5.12/2.16 proof of /export/starexec/sandbox2/benchmark/theBenchmark.xml 5.12/2.16 # AProVE Commit ID: 48fb2092695e11cc9f56e44b17a92a5f88ffb256 marcel 20180622 unpublished dirty 5.12/2.16 5.12/2.16 5.12/2.16 Termination of the given RelTRS could be proven: 5.12/2.16 5.12/2.16 (0) RelTRS 5.12/2.16 (1) RelTRSRRRProof [EQUIVALENT, 42 ms] 5.12/2.16 (2) RelTRS 5.12/2.16 (3) RelTRSRRRProof [EQUIVALENT, 21 ms] 5.12/2.16 (4) RelTRS 5.12/2.16 (5) RelTRSRRRProof [EQUIVALENT, 2 ms] 5.12/2.16 (6) RelTRS 5.12/2.16 (7) RIsEmptyProof [EQUIVALENT, 0 ms] 5.12/2.16 (8) YES 5.12/2.16 5.12/2.16 5.12/2.16 ---------------------------------------- 5.12/2.16 5.12/2.16 (0) 5.12/2.16 Obligation: 5.12/2.16 Relative term rewrite system: 5.12/2.16 The relative TRS consists of the following R rules: 5.12/2.16 5.12/2.16 s(a(x)) -> s(b(x)) 5.12/2.16 b(b(x)) -> a(x) 5.12/2.16 5.12/2.16 The relative TRS consists of the following S rules: 5.12/2.16 5.12/2.16 f(s(x), y) -> f(x, s(y)) 5.12/2.16 s(a(x)) -> a(s(x)) 5.12/2.16 s(b(x)) -> b(s(x)) 5.12/2.16 a(s(x)) -> s(a(x)) 5.12/2.16 b(s(x)) -> s(b(x)) 5.12/2.16 5.12/2.16 5.12/2.16 ---------------------------------------- 5.12/2.16 5.12/2.16 (1) RelTRSRRRProof (EQUIVALENT) 5.12/2.16 We used the following monotonic ordering for rule removal: 5.12/2.16 Polynomial interpretation [POLO]: 5.12/2.16 5.12/2.16 POL(a(x_1)) = 1 + x_1 5.12/2.16 POL(b(x_1)) = 1 + x_1 5.12/2.16 POL(f(x_1, x_2)) = x_1 + x_2 5.12/2.16 POL(s(x_1)) = x_1 5.12/2.16 With this ordering the following rules can be removed [MATRO] because they are oriented strictly: 5.12/2.16 Rules from R: 5.12/2.16 5.12/2.16 b(b(x)) -> a(x) 5.12/2.16 Rules from S: 5.12/2.16 none 5.12/2.16 5.12/2.16 5.12/2.16 5.12/2.16 5.12/2.16 ---------------------------------------- 5.12/2.16 5.12/2.16 (2) 5.12/2.16 Obligation: 5.12/2.16 Relative term rewrite system: 5.12/2.16 The relative TRS consists of the following R rules: 5.12/2.16 5.12/2.16 s(a(x)) -> s(b(x)) 5.12/2.16 5.12/2.16 The relative TRS consists of the following S rules: 5.12/2.16 5.12/2.16 f(s(x), y) -> f(x, s(y)) 5.12/2.16 s(a(x)) -> a(s(x)) 5.12/2.16 s(b(x)) -> b(s(x)) 5.12/2.16 a(s(x)) -> s(a(x)) 5.12/2.16 b(s(x)) -> s(b(x)) 5.12/2.16 5.12/2.16 5.12/2.16 ---------------------------------------- 5.12/2.16 5.12/2.16 (3) RelTRSRRRProof (EQUIVALENT) 5.12/2.16 We used the following monotonic ordering for rule removal: 5.12/2.16 s/1(YES) 5.12/2.16 a/1)YES( 5.12/2.16 b/1)YES( 5.12/2.16 f/2(YES,YES) 5.12/2.16 5.12/2.16 Quasi precedence: 5.12/2.16 f_2 > s_1 5.12/2.16 5.12/2.16 5.12/2.16 Status: 5.12/2.16 s_1: multiset status 5.12/2.16 f_2: [1,2] 5.12/2.16 5.12/2.16 With this ordering the following rules can be removed [MATRO] because they are oriented strictly: 5.12/2.16 Rules from R: 5.12/2.16 none 5.12/2.16 Rules from S: 5.12/2.16 5.12/2.16 f(s(x), y) -> f(x, s(y)) 5.12/2.16 5.12/2.16 popout

output may be truncated. 'popout' for the full output.

job log

popout

actions

all output return to TRS_Relative 2019-03-21 03.54