MAYBE 809.64/297.03 MAYBE 809.64/297.03 809.64/297.03 We are left with following problem, upon which TcT provides the 809.64/297.03 certificate MAYBE. 809.64/297.03 809.64/297.03 Strict Trs: 809.64/297.03 { tower(x) -> f(a(), x, s(0())) 809.64/297.03 , f(a(), s(x), y) -> f(b(), y, s(x)) 809.64/297.03 , f(a(), 0(), y) -> y 809.64/297.03 , f(b(), y, x) -> f(a(), half(x), exp(y)) 809.64/297.03 , half(s(s(x))) -> s(half(x)) 809.64/297.03 , half(s(0())) -> half(0()) 809.64/297.03 , half(0()) -> double(0()) 809.64/297.03 , exp(s(x)) -> double(exp(x)) 809.64/297.03 , exp(0()) -> s(0()) 809.64/297.03 , double(s(x)) -> s(s(double(x))) 809.64/297.03 , double(0()) -> 0() } 809.64/297.03 Obligation: 809.64/297.03 runtime complexity 809.64/297.03 Answer: 809.64/297.03 MAYBE 809.64/297.03 809.64/297.03 The input is overlay and right-linear. Switching to innermost 809.64/297.03 rewriting. 809.64/297.03 809.64/297.03 We are left with following problem, upon which TcT provides the 809.64/297.03 certificate MAYBE. 809.64/297.03 809.64/297.03 Strict Trs: 809.64/297.03 { tower(x) -> f(a(), x, s(0())) 809.64/297.03 , f(a(), s(x), y) -> f(b(), y, s(x)) 809.64/297.03 , f(a(), 0(), y) -> y 809.64/297.03 , f(b(), y, x) -> f(a(), half(x), exp(y)) 809.64/297.03 , half(s(s(x))) -> s(half(x)) 809.64/297.03 , half(s(0())) -> half(0()) 809.64/297.03 , half(0()) -> double(0()) 809.64/297.03 , exp(s(x)) -> double(exp(x)) 809.64/297.03 , exp(0()) -> s(0()) 809.64/297.03 , double(s(x)) -> s(s(double(x))) 809.64/297.03 , double(0()) -> 0() } 809.64/297.03 Obligation: 809.64/297.03 innermost runtime complexity 809.64/297.03 Answer: 809.64/297.03 MAYBE 809.64/297.03 809.64/297.03 None of the processors succeeded. 809.64/297.03 809.64/297.03 Details of failed attempt(s): 809.64/297.03 ----------------------------- 809.64/297.03 1) 'empty' failed due to the following reason: 809.64/297.03 809.64/297.03 Empty strict component of the problem is NOT empty. 809.64/297.03 809.64/297.03 2) 'Best' failed due to the following reason: 809.64/297.03 809.64/297.03 None of the processors succeeded. 809.64/297.03 809.64/297.03 Details of failed attempt(s): 809.64/297.03 ----------------------------- 809.64/297.03 1) 'With Problem ... (timeout of 297 seconds)' failed due to the 809.64/297.03 following reason: 809.64/297.03 809.64/297.03 Computation stopped due to timeout after 297.0 seconds. 809.64/297.03 809.64/297.03 2) 'Best' failed due to the following reason: 809.64/297.03 809.64/297.03 None of the processors succeeded. 809.64/297.03 809.64/297.03 Details of failed attempt(s): 809.64/297.03 ----------------------------- 809.64/297.03 1) 'With Problem ... (timeout of 148 seconds) (timeout of 297 809.64/297.03 seconds)' failed due to the following reason: 809.64/297.03 809.64/297.03 Computation stopped due to timeout after 148.0 seconds. 809.64/297.03 809.64/297.03 2) 'Fastest (timeout of 24 seconds) (timeout of 297 seconds)' 809.64/297.03 failed due to the following reason: 809.64/297.03 809.64/297.03 Computation stopped due to timeout after 24.0 seconds. 809.64/297.03 809.64/297.03 3) 'Best' failed due to the following reason: 809.64/297.03 809.64/297.03 None of the processors succeeded. 809.64/297.03 809.64/297.03 Details of failed attempt(s): 809.64/297.03 ----------------------------- 809.64/297.03 1) 'Polynomial Path Order (PS) (timeout of 297 seconds)' failed due 809.64/297.03 to the following reason: 809.64/297.03 809.64/297.03 The input cannot be shown compatible 809.64/297.03 809.64/297.03 2) 'bsearch-popstar (timeout of 297 seconds)' failed due to the 809.64/297.03 following reason: 809.64/297.03 809.64/297.03 The input cannot be shown compatible 809.64/297.03 809.64/297.03 809.64/297.03 809.64/297.03 809.64/297.03 809.64/297.03 Arrrr.. 810.07/297.41 EOF