MAYBE
950.48/297.10	MAYBE
950.48/297.10	
950.48/297.10	We are left with following problem, upon which TcT provides the
950.48/297.10	certificate MAYBE.
950.48/297.10	
950.48/297.10	Strict Trs:
950.48/297.10	  { active(f(X, X)) -> mark(f(a(), b()))
950.48/297.10	  , active(f(X1, X2)) -> f(active(X1), X2)
950.48/297.10	  , active(b()) -> mark(a())
950.48/297.10	  , f(mark(X1), X2) -> mark(f(X1, X2))
950.48/297.10	  , f(ok(X1), ok(X2)) -> ok(f(X1, X2))
950.48/297.10	  , proper(f(X1, X2)) -> f(proper(X1), proper(X2))
950.48/297.10	  , proper(a()) -> ok(a())
950.48/297.10	  , proper(b()) -> ok(b())
950.48/297.10	  , top(mark(X)) -> top(proper(X))
950.48/297.10	  , top(ok(X)) -> top(active(X)) }
950.48/297.10	Obligation:
950.48/297.10	  derivational complexity
950.48/297.10	Answer:
950.48/297.10	  MAYBE
950.48/297.10	
950.48/297.10	None of the processors succeeded.
950.48/297.10	
950.48/297.10	Details of failed attempt(s):
950.48/297.10	-----------------------------
950.48/297.10	1) 'Inspecting Problem... (timeout of 297 seconds)' failed due to
950.48/297.10	   the following reason:
950.48/297.10	   
950.48/297.10	   Computation stopped due to timeout after 297.0 seconds.
950.48/297.10	
950.48/297.10	2) 'Fastest (timeout of 60 seconds)' failed due to the following
950.48/297.10	   reason:
950.48/297.10	   
950.48/297.10	   Computation stopped due to timeout after 60.0 seconds.
950.48/297.10	
950.48/297.10	3) 'iteProgress (timeout of 297 seconds)' failed due to the
950.48/297.10	   following reason:
950.48/297.10	   
950.48/297.10	   Fail
950.48/297.10	
950.48/297.10	4) 'bsearch-matrix (timeout of 297 seconds)' failed due to the
950.48/297.10	   following reason:
950.48/297.10	   
950.48/297.10	   The input cannot be shown compatible
950.48/297.10	
950.48/297.10	
950.48/297.10	Arrrr..
950.48/297.12	EOF