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