MAYBE 767.85/297.12 MAYBE 767.85/297.12 767.85/297.12 We are left with following problem, upon which TcT provides the 767.85/297.12 certificate MAYBE. 767.85/297.12 767.85/297.12 Strict Trs: 767.85/297.12 { a(x1) -> g(d(x1)) 767.85/297.12 , g(g(g(x1))) -> b(b(x1)) 767.85/297.12 , b(b(x1)) -> a(g(g(x1))) 767.85/297.12 , b(b(b(x1))) -> c(d(c(x1))) 767.85/297.12 , c(d(x1)) -> g(g(x1)) } 767.85/297.12 Obligation: 767.85/297.12 derivational complexity 767.85/297.12 Answer: 767.85/297.12 MAYBE 767.85/297.12 767.85/297.12 None of the processors succeeded. 767.85/297.12 767.85/297.12 Details of failed attempt(s): 767.85/297.12 ----------------------------- 767.85/297.12 1) 'Inspecting Problem... (timeout of 297 seconds)' failed due to 767.85/297.12 the following reason: 767.85/297.12 767.85/297.12 Computation stopped due to timeout after 297.0 seconds. 767.85/297.12 767.85/297.12 2) 'Fastest (timeout of 60 seconds)' failed due to the following 767.85/297.12 reason: 767.85/297.12 767.85/297.12 Computation stopped due to timeout after 60.0 seconds. 767.85/297.12 767.85/297.12 3) 'iteProgress (timeout of 297 seconds)' failed due to the 767.85/297.12 following reason: 767.85/297.12 767.85/297.12 Fail 767.85/297.12 767.85/297.12 4) 'bsearch-matrix (timeout of 297 seconds)' failed due to the 767.85/297.12 following reason: 767.85/297.12 767.85/297.12 The input cannot be shown compatible 767.85/297.12 767.85/297.12 767.85/297.12 Arrrr.. 767.85/297.14 EOF