MAYBE 1115.41/297.02 MAYBE 1115.41/297.02 1115.41/297.02 We are left with following problem, upon which TcT provides the 1115.41/297.02 certificate MAYBE. 1115.41/297.02 1115.41/297.02 Strict Trs: 1115.41/297.02 { tower(0(x1)) -> s(0(p(s(p(s(x1)))))) 1115.41/297.02 , tower(s(x1)) -> 1115.41/297.02 p(s(p(s(twoto(p(s(p(s(tower(p(s(p(s(x1)))))))))))))) 1115.41/297.02 , p(0(x1)) -> 0(s(s(s(s(s(s(s(s(x1))))))))) 1115.41/297.02 , p(s(x1)) -> x1 1115.41/297.02 , p(p(s(x1))) -> p(x1) 1115.41/297.02 , twoto(0(x1)) -> s(0(x1)) 1115.41/297.02 , twoto(s(x1)) -> 1115.41/297.02 p(p(s(p(p(p(s(s(p(s(s(p(s(s(p(s(twice(p(s(p(s(p(p(p(s(s(s(twoto(p(s(p(s(x1)))))))))))))))))))))))))))))))) 1115.41/297.02 , twice(0(x1)) -> 0(x1) 1115.41/297.02 , twice(s(x1)) -> 1115.41/297.02 p(p(p(s(s(s(s(s(twice(p(p(p(s(s(s(x1))))))))))))))) } 1115.41/297.02 Obligation: 1115.41/297.02 derivational complexity 1115.41/297.02 Answer: 1115.41/297.02 MAYBE 1115.41/297.02 1115.41/297.02 None of the processors succeeded. 1115.41/297.02 1115.41/297.02 Details of failed attempt(s): 1115.41/297.02 ----------------------------- 1115.41/297.02 1) 'Inspecting Problem... (timeout of 297 seconds)' failed due to 1115.41/297.02 the following reason: 1115.41/297.02 1115.41/297.02 Computation stopped due to timeout after 297.0 seconds. 1115.41/297.02 1115.41/297.02 2) 'bsearch-matrix (timeout of 297 seconds)' failed due to the 1115.41/297.02 following reason: 1115.41/297.02 1115.41/297.02 Computation stopped due to timeout after 297.0 seconds. 1115.41/297.02 1115.41/297.02 3) 'iteProgress (timeout of 297 seconds)' failed due to the 1115.41/297.02 following reason: 1115.41/297.02 1115.41/297.02 Computation stopped due to timeout after 297.0 seconds. 1115.41/297.02 1115.41/297.02 4) 'Fastest (timeout of 60 seconds)' failed due to the following 1115.41/297.02 reason: 1115.41/297.02 1115.41/297.02 Computation stopped due to timeout after 60.0 seconds. 1115.41/297.02 1115.41/297.02 1115.41/297.02 Arrrr.. 1115.96/297.57 EOF