MAYBE
1159.48/297.15	MAYBE
1159.48/297.15	
1159.48/297.15	We are left with following problem, upon which TcT provides the
1159.48/297.15	certificate MAYBE.
1159.48/297.15	
1159.48/297.15	Strict Trs:
1159.48/297.15	  { p(p(s(x1))) -> p(x1)
1159.48/297.15	  , p(0(x1)) -> 0(s(s(p(x1))))
1159.48/297.15	  , p(s(x1)) -> x1
1159.48/297.15	  , f(s(x1)) -> p(s(g(p(s(s(x1))))))
1159.48/297.15	  , g(s(x1)) -> p(p(s(s(s(j(s(p(s(p(s(x1)))))))))))
1159.48/297.15	  , j(s(x1)) -> p(s(s(p(s(f(p(s(p(p(s(x1)))))))))))
1159.48/297.15	  , half(0(x1)) -> 0(s(s(half(p(s(p(s(x1))))))))
1159.48/297.15	  , half(s(s(x1))) -> s(half(p(p(s(s(x1))))))
1159.48/297.15	  , rd(0(x1)) -> 0(s(0(0(0(0(s(0(rd(x1))))))))) }
1159.48/297.15	Obligation:
1159.48/297.15	  derivational complexity
1159.48/297.15	Answer:
1159.48/297.15	  MAYBE
1159.48/297.15	
1159.48/297.15	None of the processors succeeded.
1159.48/297.15	
1159.48/297.15	Details of failed attempt(s):
1159.48/297.15	-----------------------------
1159.48/297.15	1) 'Inspecting Problem... (timeout of 297 seconds)' failed due to
1159.48/297.15	   the following reason:
1159.48/297.15	   
1159.48/297.15	   Computation stopped due to timeout after 297.0 seconds.
1159.48/297.15	
1159.48/297.15	2) 'iteProgress (timeout of 297 seconds)' failed due to the
1159.48/297.15	   following reason:
1159.48/297.15	   
1159.48/297.15	   Computation stopped due to timeout after 297.0 seconds.
1159.48/297.15	
1159.48/297.15	3) 'bsearch-matrix (timeout of 297 seconds)' failed due to the
1159.48/297.15	   following reason:
1159.48/297.15	   
1159.48/297.15	   Computation stopped due to timeout after 297.0 seconds.
1159.48/297.15	
1159.48/297.15	4) 'Fastest (timeout of 60 seconds)' failed due to the following
1159.48/297.15	   reason:
1159.48/297.15	   
1159.48/297.15	   Computation stopped due to timeout after 60.0 seconds.
1159.48/297.15	
1159.48/297.15	
1159.48/297.15	Arrrr..
1160.24/297.71	EOF