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