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