MAYBE 839.27/297.09 MAYBE 839.27/297.09 839.27/297.09 We are left with following problem, upon which TcT provides the 839.27/297.09 certificate MAYBE. 839.27/297.09 839.27/297.09 Strict Trs: 839.27/297.09 { active(first(X1, X2)) -> first(X1, active(X2)) 839.27/297.09 , active(first(X1, X2)) -> first(active(X1), X2) 839.27/297.09 , active(first(0(), X)) -> mark(nil()) 839.27/297.09 , active(first(s(X), cons(Y, Z))) -> mark(cons(Y, first(X, Z))) 839.27/297.09 , active(s(X)) -> s(active(X)) 839.27/297.09 , active(cons(X1, X2)) -> cons(active(X1), X2) 839.27/297.09 , active(from(X)) -> mark(cons(X, from(s(X)))) 839.27/297.09 , active(from(X)) -> from(active(X)) 839.27/297.09 , first(X1, mark(X2)) -> mark(first(X1, X2)) 839.27/297.09 , first(mark(X1), X2) -> mark(first(X1, X2)) 839.27/297.09 , first(ok(X1), ok(X2)) -> ok(first(X1, X2)) 839.27/297.09 , s(mark(X)) -> mark(s(X)) 839.27/297.09 , s(ok(X)) -> ok(s(X)) 839.27/297.09 , cons(mark(X1), X2) -> mark(cons(X1, X2)) 839.27/297.09 , cons(ok(X1), ok(X2)) -> ok(cons(X1, X2)) 839.27/297.09 , from(mark(X)) -> mark(from(X)) 839.27/297.09 , from(ok(X)) -> ok(from(X)) 839.27/297.09 , proper(first(X1, X2)) -> first(proper(X1), proper(X2)) 839.27/297.09 , proper(0()) -> ok(0()) 839.27/297.09 , proper(nil()) -> ok(nil()) 839.27/297.09 , proper(s(X)) -> s(proper(X)) 839.27/297.09 , proper(cons(X1, X2)) -> cons(proper(X1), proper(X2)) 839.27/297.09 , proper(from(X)) -> from(proper(X)) 839.27/297.09 , top(mark(X)) -> top(proper(X)) 839.27/297.09 , top(ok(X)) -> top(active(X)) } 839.27/297.09 Obligation: 839.27/297.09 innermost runtime complexity 839.27/297.09 Answer: 839.27/297.09 MAYBE 839.27/297.09 839.27/297.09 None of the processors succeeded. 839.27/297.09 839.27/297.09 Details of failed attempt(s): 839.27/297.09 ----------------------------- 839.27/297.09 1) 'empty' failed due to the following reason: 839.27/297.09 839.27/297.09 Empty strict component of the problem is NOT empty. 839.27/297.09 839.27/297.09 2) 'Best' failed due to the following reason: 839.27/297.09 839.27/297.09 None of the processors succeeded. 839.27/297.09 839.27/297.09 Details of failed attempt(s): 839.27/297.09 ----------------------------- 839.27/297.09 1) 'With Problem ... (timeout of 297 seconds)' failed due to the 839.27/297.09 following reason: 839.27/297.09 839.27/297.09 Computation stopped due to timeout after 297.0 seconds. 839.27/297.09 839.27/297.09 2) 'Best' failed due to the following reason: 839.27/297.09 839.27/297.09 None of the processors succeeded. 839.27/297.09 839.27/297.09 Details of failed attempt(s): 839.27/297.09 ----------------------------- 839.27/297.09 1) 'With Problem ... (timeout of 148 seconds) (timeout of 297 839.27/297.09 seconds)' failed due to the following reason: 839.27/297.09 839.27/297.09 Computation stopped due to timeout after 148.0 seconds. 839.27/297.09 839.27/297.09 2) 'Best' failed due to the following reason: 839.27/297.09 839.27/297.09 None of the processors succeeded. 839.27/297.09 839.27/297.09 Details of failed attempt(s): 839.27/297.09 ----------------------------- 839.27/297.09 1) 'bsearch-popstar (timeout of 297 seconds)' failed due to the 839.27/297.09 following reason: 839.27/297.09 839.27/297.09 The input cannot be shown compatible 839.27/297.09 839.27/297.09 2) 'Polynomial Path Order (PS) (timeout of 297 seconds)' failed due 839.27/297.09 to the following reason: 839.27/297.09 839.27/297.09 The input cannot be shown compatible 839.27/297.09 839.27/297.09 839.27/297.09 3) 'Fastest (timeout of 24 seconds) (timeout of 297 seconds)' 839.27/297.09 failed due to the following reason: 839.27/297.09 839.27/297.09 None of the processors succeeded. 839.27/297.09 839.27/297.09 Details of failed attempt(s): 839.27/297.09 ----------------------------- 839.27/297.09 1) 'Bounds with perSymbol-enrichment and initial automaton 'match'' 839.27/297.09 failed due to the following reason: 839.27/297.09 839.27/297.09 match-boundness of the problem could not be verified. 839.27/297.09 839.27/297.09 2) 'Bounds with minimal-enrichment and initial automaton 'match'' 839.27/297.09 failed due to the following reason: 839.27/297.09 839.27/297.09 match-boundness of the problem could not be verified. 839.27/297.09 839.27/297.09 839.27/297.09 839.27/297.09 839.27/297.09 839.27/297.09 Arrrr.. 839.37/297.16 EOF