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