MAYBE 1012.77/297.04 MAYBE 1012.77/297.04 1012.77/297.04 We are left with following problem, upon which TcT provides the 1012.77/297.04 certificate MAYBE. 1012.77/297.04 1012.77/297.04 Strict Trs: 1012.77/297.04 { a__fact(X) -> 1012.77/297.04 a__if(a__zero(mark(X)), s(0()), prod(X, fact(p(X)))) 1012.77/297.04 , a__fact(X) -> fact(X) 1012.77/297.04 , a__if(X1, X2, X3) -> if(X1, X2, X3) 1012.77/297.04 , a__if(true(), X, Y) -> mark(X) 1012.77/297.04 , a__if(false(), X, Y) -> mark(Y) 1012.77/297.04 , a__zero(X) -> zero(X) 1012.77/297.04 , a__zero(s(X)) -> false() 1012.77/297.04 , a__zero(0()) -> true() 1012.77/297.04 , mark(s(X)) -> s(mark(X)) 1012.77/297.04 , mark(0()) -> 0() 1012.77/297.04 , mark(prod(X1, X2)) -> a__prod(mark(X1), mark(X2)) 1012.77/297.04 , mark(fact(X)) -> a__fact(mark(X)) 1012.77/297.04 , mark(p(X)) -> a__p(mark(X)) 1012.77/297.04 , mark(true()) -> true() 1012.77/297.04 , mark(false()) -> false() 1012.77/297.04 , mark(if(X1, X2, X3)) -> a__if(mark(X1), X2, X3) 1012.77/297.04 , mark(zero(X)) -> a__zero(mark(X)) 1012.77/297.04 , mark(add(X1, X2)) -> a__add(mark(X1), mark(X2)) 1012.77/297.04 , a__add(X1, X2) -> add(X1, X2) 1012.77/297.04 , a__add(s(X), Y) -> s(a__add(mark(X), mark(Y))) 1012.77/297.04 , a__add(0(), X) -> mark(X) 1012.77/297.04 , a__prod(X1, X2) -> prod(X1, X2) 1012.77/297.04 , a__prod(s(X), Y) -> a__add(mark(Y), a__prod(mark(X), mark(Y))) 1012.77/297.04 , a__prod(0(), X) -> 0() 1012.77/297.04 , a__p(X) -> p(X) 1012.77/297.04 , a__p(s(X)) -> mark(X) } 1012.77/297.04 Obligation: 1012.77/297.04 innermost runtime complexity 1012.77/297.04 Answer: 1012.77/297.04 MAYBE 1012.77/297.04 1012.77/297.04 None of the processors succeeded. 1012.77/297.04 1012.77/297.04 Details of failed attempt(s): 1012.77/297.04 ----------------------------- 1012.77/297.04 1) 'empty' failed due to the following reason: 1012.77/297.04 1012.77/297.04 Empty strict component of the problem is NOT empty. 1012.77/297.04 1012.77/297.04 2) 'Best' failed due to the following reason: 1012.77/297.04 1012.77/297.04 None of the processors succeeded. 1012.77/297.04 1012.77/297.04 Details of failed attempt(s): 1012.77/297.04 ----------------------------- 1012.77/297.04 1) 'With Problem ... (timeout of 297 seconds)' failed due to the 1012.77/297.04 following reason: 1012.77/297.04 1012.77/297.04 Computation stopped due to timeout after 297.0 seconds. 1012.77/297.04 1012.77/297.04 2) 'Best' failed due to the following reason: 1012.77/297.04 1012.77/297.04 None of the processors succeeded. 1012.77/297.04 1012.77/297.04 Details of failed attempt(s): 1012.77/297.04 ----------------------------- 1012.77/297.04 1) 'With Problem ... (timeout of 148 seconds) (timeout of 297 1012.77/297.04 seconds)' failed due to the following reason: 1012.77/297.04 1012.77/297.04 Computation stopped due to timeout after 148.0 seconds. 1012.77/297.04 1012.77/297.04 2) 'Best' failed due to the following reason: 1012.77/297.04 1012.77/297.04 None of the processors succeeded. 1012.77/297.04 1012.77/297.04 Details of failed attempt(s): 1012.77/297.04 ----------------------------- 1012.77/297.04 1) 'bsearch-popstar (timeout of 297 seconds)' failed due to the 1012.77/297.04 following reason: 1012.77/297.04 1012.77/297.04 The input cannot be shown compatible 1012.77/297.04 1012.77/297.04 2) 'Polynomial Path Order (PS) (timeout of 297 seconds)' failed due 1012.77/297.04 to the following reason: 1012.77/297.04 1012.77/297.04 The input cannot be shown compatible 1012.77/297.04 1012.77/297.04 1012.77/297.04 3) 'Fastest (timeout of 24 seconds) (timeout of 297 seconds)' 1012.77/297.04 failed due to the following reason: 1012.77/297.04 1012.77/297.04 None of the processors succeeded. 1012.77/297.04 1012.77/297.04 Details of failed attempt(s): 1012.77/297.04 ----------------------------- 1012.77/297.04 1) 'Bounds with minimal-enrichment and initial automaton 'match'' 1012.77/297.04 failed due to the following reason: 1012.77/297.04 1012.77/297.04 match-boundness of the problem could not be verified. 1012.77/297.04 1012.77/297.04 2) 'Bounds with perSymbol-enrichment and initial automaton 'match'' 1012.77/297.04 failed due to the following reason: 1012.77/297.04 1012.77/297.04 match-boundness of the problem could not be verified. 1012.77/297.04 1012.77/297.04 1012.77/297.04 1012.77/297.04 1012.77/297.04 1012.77/297.04 Arrrr.. 1014.94/299.14 EOF