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