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