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