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