MAYBE
1096.60/297.02	MAYBE
1096.60/297.02	
1096.60/297.02	We are left with following problem, upon which TcT provides the
1096.60/297.02	certificate MAYBE.
1096.60/297.02	
1096.60/297.02	Strict Trs:
1096.60/297.02	  { i(x, x) -> i(a(), b())
1096.60/297.02	  , g(x, x) -> g(a(), b())
1096.60/297.02	  , g(a(), g(x, g(b(), g(a(), g(x, y))))) ->
1096.60/297.02	    g(a(), g(a(), g(a(), g(x, g(b(), g(b(), y))))))
1096.60/297.02	  , h(i(x, y)) -> i(i(c(), h(h(y))), x)
1096.60/297.02	  , h(g(x, s(y))) -> h(g(s(x), y))
1096.60/297.02	  , h(s(f(x))) -> h(f(x))
1096.60/297.02	  , f(g(s(x), y)) -> f(g(x, s(y)))
1096.60/297.02	  , f(s(x)) -> s(s(f(h(s(x))))) }
1096.60/297.02	Obligation:
1096.60/297.02	  derivational complexity
1096.60/297.02	Answer:
1096.60/297.02	  MAYBE
1096.60/297.02	
1096.60/297.02	None of the processors succeeded.
1096.60/297.02	
1096.60/297.02	Details of failed attempt(s):
1096.60/297.02	-----------------------------
1096.60/297.02	1) 'bsearch-matrix (timeout of 297 seconds)' failed due to the
1096.60/297.02	   following reason:
1096.60/297.02	   
1096.60/297.02	   Computation stopped due to timeout after 297.0 seconds.
1096.60/297.02	
1096.60/297.02	2) 'Inspecting Problem... (timeout of 297 seconds)' failed due to
1096.60/297.02	   the following reason:
1096.60/297.02	   
1096.60/297.02	   Computation stopped due to timeout after 297.0 seconds.
1096.60/297.02	
1096.60/297.02	3) 'iteProgress (timeout of 297 seconds)' failed due to the
1096.60/297.02	   following reason:
1096.60/297.02	   
1096.60/297.02	   Fail
1096.60/297.02	
1096.60/297.02	4) 'Fastest (timeout of 60 seconds)' failed due to the following
1096.60/297.02	   reason:
1096.60/297.02	   
1096.60/297.02	   Computation stopped due to timeout after 60.0 seconds.
1096.60/297.02	
1096.60/297.02	
1096.60/297.02	Arrrr..
1096.73/297.14	EOF