details

property	value
status	complete
benchmark	15.xml
ran by	Akihisa Yamada
cpu timeout	1200 seconds
wallclock timeout	300 seconds
memory limit	137438953472 bytes
execution host	n149.star.cs.uiowa.edu
space	Various_04

run statistics

property	value
solver	AProVE
configuration	complexity
runtime (wallclock)	1.97418 seconds
cpu usage	4.89456
user time	4.65199
system time	0.242566
max virtual memory	1.8343924E7
max residence set size	505500.0

stage attributes

key	value
starexec-result	WORST_CASE(Omega(n^1), O(n^1))

output

WORST_CASE(Omega(n^1), O(n^1)) proof of /export/starexec/sandbox/benchmark/theBenchmark.xml # AProVE Commit ID: 794c25de1cacf0d048858bcd21c9a779e1221865 marcel 20200619 unpublished dirty The Runtime Complexity (full) of the given CpxTRS could be proven to be BOUNDS(n^1, n^1). (0) CpxTRS (1) RelTrsToTrsProof [UPPER BOUND(ID), 0 ms] (2) CpxTRS (3) CpxTrsMatchBoundsProof [FINISHED, 0 ms] (4) BOUNDS(1, n^1) (5) RenamingProof [BOTH BOUNDS(ID, ID), 0 ms] (6) CpxTRS (7) TypeInferenceProof [BOTH BOUNDS(ID, ID), 0 ms] (8) typed CpxTrs (9) OrderProof [LOWER BOUND(ID), 0 ms] (10) typed CpxTrs (11) RewriteLemmaProof [LOWER BOUND(ID), 200 ms] (12) proven lower bound (13) LowerBoundPropagationProof [FINISHED, 0 ms] (14) BOUNDS(n^1, INF) ---------------------------------------- (0) Obligation: The Runtime Complexity (full) of the given CpxTRS could be proven to be BOUNDS(n^1, n^1). The TRS R consists of the following rules: f(s(x)) -> s(s(f(p(s(x))))) f(0) -> 0 p(s(x)) -> x S is empty. Rewrite Strategy: FULL ---------------------------------------- (1) RelTrsToTrsProof (UPPER BOUND(ID)) transformed relative TRS to TRS ---------------------------------------- (2) Obligation: The Runtime Complexity (full) of the given CpxTRS could be proven to be BOUNDS(1, n^1). The TRS R consists of the following rules: f(s(x)) -> s(s(f(p(s(x))))) f(0) -> 0 p(s(x)) -> x S is empty. Rewrite Strategy: FULL ---------------------------------------- (3) CpxTrsMatchBoundsProof (FINISHED) A linear upper bound on the runtime complexity of the TRS R could be shown with a Match Bound [MATCHBOUNDS1,MATCHBOUNDS2] of 2. The certificate found is represented by the following graph. "[1, 2, 3, 4, 5, 6, 7, 8, 9, 10] {(1,2,[f_1|0, p_1|0, 0|1, s_1|1]), (1,3,[s_1|1]), (2,2,[s_1|0, 0|0]), (3,4,[s_1|1]), (4,5,[f_1|1]), (4,7,[s_1|2]), (4,2,[0|2]), (5,6,[p_1|1]), (5,2,[s_1|1, 0|1]), (6,2,[s_1|1]), (7,8,[s_1|2]), (8,9,[f_1|2]), (8,7,[s_1|2]), (8,2,[0|2]), (9,10,[p_1|2]), (9,2,[s_1|1, 0|1]), (10,2,[s_1|2])}" ---------------------------------------- (4) BOUNDS(1, n^1) ---------------------------------------- (5) RenamingProof (BOTH BOUNDS(ID, ID)) Renamed function symbols to avoid clashes with predefined symbol. ---------------------------------------- (6) Obligation: The Runtime Complexity (full) of the given CpxTRS could be proven to be BOUNDS(n^1, INF). The TRS R consists of the following rules: f(s(x)) -> s(s(f(p(s(x))))) f(0') -> 0' p(s(x)) -> x S is empty. Rewrite Strategy: FULL ---------------------------------------- (7) TypeInferenceProof (BOTH BOUNDS(ID, ID)) Infered types. ---------------------------------------- (8) Obligation: TRS: Rules: popout

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

job log

popout

actions

all output return to Runtime Complexity: TRS