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