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