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