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