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