MAYBE 1130.36/297.97 MAYBE 1130.36/297.97 1130.36/297.97 We are left with following problem, upon which TcT provides the 1130.36/297.97 certificate MAYBE. 1130.36/297.97 1130.36/297.97 Strict Trs: 1130.36/297.97 { fib(N) -> sel(N, fib1(s(0()), s(0()))) 1130.36/297.97 , sel(s(N), cons(X, XS)) -> sel(N, activate(XS)) 1130.36/297.97 , sel(0(), cons(X, XS)) -> X 1130.36/297.97 , fib1(X, Y) -> cons(X, n__fib1(Y, add(X, Y))) 1130.36/297.97 , fib1(X1, X2) -> n__fib1(X1, X2) 1130.36/297.97 , add(s(X), Y) -> s(add(X, Y)) 1130.36/297.97 , add(0(), X) -> X 1130.36/297.97 , activate(X) -> X 1130.36/297.97 , activate(n__fib1(X1, X2)) -> fib1(X1, X2) } 1130.36/297.97 Obligation: 1130.36/297.97 innermost runtime complexity 1130.36/297.97 Answer: 1130.36/297.97 MAYBE 1130.36/297.97 1130.36/297.97 None of the processors succeeded. 1130.36/297.97 1130.36/297.97 Details of failed attempt(s): 1130.36/297.97 ----------------------------- 1130.36/297.97 1) 'empty' failed due to the following reason: 1130.36/297.97 1130.36/297.97 Empty strict component of the problem is NOT empty. 1130.36/297.97 1130.36/297.97 2) 'Best' failed due to the following reason: 1130.36/297.97 1130.36/297.97 None of the processors succeeded. 1130.36/297.97 1130.36/297.97 Details of failed attempt(s): 1130.36/297.97 ----------------------------- 1130.36/297.97 1) 'With Problem ... (timeout of 297 seconds)' failed due to the 1130.36/297.97 following reason: 1130.36/297.97 1130.36/297.97 Computation stopped due to timeout after 297.0 seconds. 1130.36/297.97 1130.36/297.97 2) 'Best' failed due to the following reason: 1130.36/297.97 1130.36/297.97 None of the processors succeeded. 1130.36/297.97 1130.36/297.97 Details of failed attempt(s): 1130.36/297.97 ----------------------------- 1130.36/297.97 1) 'With Problem ... (timeout of 148 seconds) (timeout of 297 1130.36/297.97 seconds)' failed due to the following reason: 1130.36/297.97 1130.36/297.97 Computation stopped due to timeout after 148.0 seconds. 1130.36/297.97 1130.36/297.97 2) 'Best' failed due to the following reason: 1130.36/297.97 1130.36/297.97 None of the processors succeeded. 1130.36/297.97 1130.36/297.97 Details of failed attempt(s): 1130.36/297.97 ----------------------------- 1130.36/297.97 1) 'bsearch-popstar (timeout of 297 seconds)' failed due to the 1130.36/297.97 following reason: 1130.36/297.97 1130.36/297.97 The input cannot be shown compatible 1130.36/297.97 1130.36/297.97 2) 'Polynomial Path Order (PS) (timeout of 297 seconds)' failed due 1130.36/297.97 to the following reason: 1130.36/297.97 1130.36/297.97 The input cannot be shown compatible 1130.36/297.97 1130.36/297.97 1130.36/297.97 3) 'Fastest (timeout of 24 seconds) (timeout of 297 seconds)' 1130.36/297.97 failed due to the following reason: 1130.36/297.97 1130.36/297.97 None of the processors succeeded. 1130.36/297.97 1130.36/297.97 Details of failed attempt(s): 1130.36/297.97 ----------------------------- 1130.36/297.97 1) 'Bounds with minimal-enrichment and initial automaton 'match'' 1130.36/297.97 failed due to the following reason: 1130.36/297.97 1130.36/297.97 match-boundness of the problem could not be verified. 1130.36/297.97 1130.36/297.97 2) 'Bounds with perSymbol-enrichment and initial automaton 'match'' 1130.36/297.97 failed due to the following reason: 1130.36/297.97 1130.36/297.97 match-boundness of the problem could not be verified. 1130.36/297.97 1130.36/297.97 1130.36/297.97 1130.36/297.97 1130.36/297.97 1130.36/297.97 Arrrr.. 1130.88/298.20 EOF