MAYBE 816.03/297.03 MAYBE 816.03/297.03 816.03/297.03 We are left with following problem, upon which TcT provides the 816.03/297.03 certificate MAYBE. 816.03/297.03 816.03/297.03 Strict Trs: 816.03/297.03 { from(X) -> cons(X, n__from(n__s(X))) 816.03/297.03 , from(X) -> n__from(X) 816.03/297.03 , sel(0(), cons(X, Y)) -> X 816.03/297.03 , sel(s(X), cons(Y, Z)) -> sel(X, activate(Z)) 816.03/297.03 , s(X) -> n__s(X) 816.03/297.03 , activate(X) -> X 816.03/297.03 , activate(n__from(X)) -> from(activate(X)) 816.03/297.03 , activate(n__s(X)) -> s(activate(X)) } 816.03/297.03 Obligation: 816.03/297.03 runtime complexity 816.03/297.03 Answer: 816.03/297.03 MAYBE 816.03/297.03 816.03/297.03 None of the processors succeeded. 816.03/297.03 816.03/297.03 Details of failed attempt(s): 816.03/297.03 ----------------------------- 816.03/297.03 1) 'With Problem ... (timeout of 297 seconds)' failed due to the 816.03/297.03 following reason: 816.03/297.03 816.03/297.03 Computation stopped due to timeout after 297.0 seconds. 816.03/297.03 816.03/297.03 2) 'Best' failed due to the following reason: 816.03/297.03 816.03/297.03 None of the processors succeeded. 816.03/297.03 816.03/297.03 Details of failed attempt(s): 816.03/297.03 ----------------------------- 816.03/297.03 1) 'With Problem ... (timeout of 148 seconds) (timeout of 297 816.03/297.03 seconds)' failed due to the following reason: 816.03/297.03 816.03/297.03 None of the processors succeeded. 816.03/297.03 816.03/297.03 Details of failed attempt(s): 816.03/297.03 ----------------------------- 816.03/297.03 1) 'empty' failed due to the following reason: 816.03/297.03 816.03/297.03 Empty strict component of the problem is NOT empty. 816.03/297.03 816.03/297.03 2) 'With Problem ...' failed due to the following reason: 816.03/297.03 816.03/297.03 None of the processors succeeded. 816.03/297.03 816.03/297.03 Details of failed attempt(s): 816.03/297.03 ----------------------------- 816.03/297.03 1) 'empty' failed due to the following reason: 816.03/297.03 816.03/297.03 Empty strict component of the problem is NOT empty. 816.03/297.03 816.03/297.03 2) 'Fastest' failed due to the following reason: 816.03/297.03 816.03/297.03 None of the processors succeeded. 816.03/297.03 816.03/297.03 Details of failed attempt(s): 816.03/297.03 ----------------------------- 816.03/297.03 1) 'With Problem ...' failed due to the following reason: 816.03/297.03 816.03/297.03 None of the processors succeeded. 816.03/297.03 816.03/297.03 Details of failed attempt(s): 816.03/297.03 ----------------------------- 816.03/297.03 1) 'empty' failed due to the following reason: 816.03/297.03 816.03/297.03 Empty strict component of the problem is NOT empty. 816.03/297.03 816.03/297.03 2) 'With Problem ...' failed due to the following reason: 816.03/297.03 816.03/297.03 None of the processors succeeded. 816.03/297.03 816.03/297.03 Details of failed attempt(s): 816.03/297.03 ----------------------------- 816.03/297.03 1) 'empty' failed due to the following reason: 816.03/297.03 816.03/297.03 Empty strict component of the problem is NOT empty. 816.03/297.03 816.03/297.03 2) 'With Problem ...' failed due to the following reason: 816.03/297.03 816.03/297.03 None of the processors succeeded. 816.03/297.03 816.03/297.03 Details of failed attempt(s): 816.03/297.03 ----------------------------- 816.03/297.03 1) 'empty' failed due to the following reason: 816.03/297.03 816.03/297.03 Empty strict component of the problem is NOT empty. 816.03/297.03 816.03/297.03 2) 'With Problem ...' failed due to the following reason: 816.03/297.03 816.03/297.03 Empty strict component of the problem is NOT empty. 816.03/297.03 816.03/297.03 816.03/297.03 816.03/297.03 816.03/297.03 2) 'With Problem ...' failed due to the following reason: 816.03/297.03 816.03/297.03 None of the processors succeeded. 816.03/297.03 816.03/297.03 Details of failed attempt(s): 816.03/297.03 ----------------------------- 816.03/297.03 1) 'empty' failed due to the following reason: 816.03/297.03 816.03/297.03 Empty strict component of the problem is NOT empty. 816.03/297.03 816.03/297.03 2) 'With Problem ...' failed due to the following reason: 816.03/297.03 816.03/297.03 Empty strict component of the problem is NOT empty. 816.03/297.03 816.03/297.03 816.03/297.03 816.03/297.03 816.03/297.03 816.03/297.03 2) 'Fastest (timeout of 24 seconds) (timeout of 297 seconds)' 816.03/297.03 failed due to the following reason: 816.03/297.03 816.03/297.03 None of the processors succeeded. 816.03/297.03 816.03/297.03 Details of failed attempt(s): 816.03/297.03 ----------------------------- 816.03/297.03 1) 'Bounds with minimal-enrichment and initial automaton 'match'' 816.03/297.03 failed due to the following reason: 816.03/297.03 816.03/297.03 match-boundness of the problem could not be verified. 816.03/297.03 816.03/297.03 2) 'Bounds with perSymbol-enrichment and initial automaton 'match'' 816.03/297.03 failed due to the following reason: 816.03/297.03 816.03/297.03 match-boundness of the problem could not be verified. 816.03/297.03 816.03/297.03 816.03/297.03 3) 'Best' failed due to the following reason: 816.03/297.03 816.03/297.03 None of the processors succeeded. 816.03/297.03 816.03/297.03 Details of failed attempt(s): 816.03/297.03 ----------------------------- 816.03/297.03 1) 'bsearch-popstar (timeout of 297 seconds)' failed due to the 816.03/297.03 following reason: 816.03/297.03 816.03/297.03 The processor is inapplicable, reason: 816.03/297.03 Processor only applicable for innermost runtime complexity analysis 816.03/297.03 816.03/297.03 2) 'Polynomial Path Order (PS) (timeout of 297 seconds)' failed due 816.03/297.03 to the following reason: 816.03/297.03 816.03/297.03 The processor is inapplicable, reason: 816.03/297.03 Processor only applicable for innermost runtime complexity analysis 816.03/297.03 816.03/297.03 816.03/297.03 816.03/297.03 3) 'Weak Dependency Pairs (timeout of 297 seconds)' failed due to 816.03/297.03 the following reason: 816.03/297.03 816.03/297.03 We add the following weak dependency pairs: 816.03/297.03 816.03/297.03 Strict DPs: 816.03/297.03 { from^#(X) -> c_1(X, X) 816.03/297.03 , from^#(X) -> c_2(X) 816.03/297.03 , sel^#(0(), cons(X, Y)) -> c_3(X) 816.03/297.03 , sel^#(s(X), cons(Y, Z)) -> c_4(sel^#(X, activate(Z))) 816.03/297.03 , s^#(X) -> c_5(X) 816.03/297.03 , activate^#(X) -> c_6(X) 816.03/297.03 , activate^#(n__from(X)) -> c_7(from^#(activate(X))) 816.03/297.03 , activate^#(n__s(X)) -> c_8(s^#(activate(X))) } 816.03/297.03 816.03/297.03 and mark the set of starting terms. 816.03/297.03 816.03/297.03 We are left with following problem, upon which TcT provides the 816.03/297.03 certificate MAYBE. 816.03/297.03 816.03/297.03 Strict DPs: 816.03/297.03 { from^#(X) -> c_1(X, X) 816.03/297.03 , from^#(X) -> c_2(X) 816.03/297.03 , sel^#(0(), cons(X, Y)) -> c_3(X) 816.03/297.03 , sel^#(s(X), cons(Y, Z)) -> c_4(sel^#(X, activate(Z))) 816.03/297.03 , s^#(X) -> c_5(X) 816.03/297.03 , activate^#(X) -> c_6(X) 816.03/297.03 , activate^#(n__from(X)) -> c_7(from^#(activate(X))) 816.03/297.03 , activate^#(n__s(X)) -> c_8(s^#(activate(X))) } 816.03/297.03 Strict Trs: 816.03/297.03 { from(X) -> cons(X, n__from(n__s(X))) 816.03/297.03 , from(X) -> n__from(X) 816.03/297.03 , sel(0(), cons(X, Y)) -> X 816.03/297.03 , sel(s(X), cons(Y, Z)) -> sel(X, activate(Z)) 816.03/297.03 , s(X) -> n__s(X) 816.03/297.03 , activate(X) -> X 816.03/297.03 , activate(n__from(X)) -> from(activate(X)) 816.03/297.03 , activate(n__s(X)) -> s(activate(X)) } 816.03/297.03 Obligation: 816.03/297.03 runtime complexity 816.03/297.03 Answer: 816.03/297.03 MAYBE 816.03/297.03 816.03/297.03 Empty strict component of the problem is NOT empty. 816.03/297.03 816.03/297.03 816.03/297.03 Arrrr.. 816.25/297.29 EOF