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