MAYBE
1109.85/297.05	MAYBE
1109.85/297.05	
1109.85/297.05	We are left with following problem, upon which TcT provides the
1109.85/297.05	certificate MAYBE.
1109.85/297.05	
1109.85/297.05	Strict Trs:
1109.85/297.05	  { a(b(c(a(x1)))) -> b(a(c(b(a(b(x1))))))
1109.85/297.05	  , a(d(x1)) -> c(x1)
1109.85/297.05	  , a(f(f(x1))) -> g(x1)
1109.85/297.05	  , b(g(x1)) -> g(b(x1))
1109.85/297.05	  , c(x1) -> f(f(x1))
1109.85/297.05	  , c(a(c(x1))) -> b(c(a(b(c(x1)))))
1109.85/297.05	  , c(d(x1)) -> a(a(x1))
1109.85/297.05	  , g(x1) -> c(a(x1))
1109.85/297.05	  , g(x1) -> d(d(d(d(x1)))) }
1109.85/297.05	Obligation:
1109.85/297.05	  derivational complexity
1109.85/297.05	Answer:
1109.85/297.05	  MAYBE
1109.85/297.05	
1109.85/297.05	None of the processors succeeded.
1109.85/297.05	
1109.85/297.05	Details of failed attempt(s):
1109.85/297.05	-----------------------------
1109.85/297.05	1) 'Inspecting Problem... (timeout of 297 seconds)' failed due to
1109.85/297.05	   the following reason:
1109.85/297.05	   
1109.85/297.05	   Computation stopped due to timeout after 297.0 seconds.
1109.85/297.05	
1109.85/297.05	2) 'iteProgress (timeout of 297 seconds)' failed due to the
1109.85/297.05	   following reason:
1109.85/297.05	   
1109.85/297.05	   Fail
1109.85/297.05	
1109.85/297.05	3) 'Fastest (timeout of 60 seconds)' failed due to the following
1109.85/297.05	   reason:
1109.85/297.05	   
1109.85/297.05	   Computation stopped due to timeout after 60.0 seconds.
1109.85/297.05	
1109.85/297.05	4) 'bsearch-matrix (timeout of 297 seconds)' failed due to the
1109.85/297.05	   following reason:
1109.85/297.05	   
1109.85/297.05	   Following exception was raised:
1109.85/297.05	     stack overflow
1109.85/297.05	
1109.85/297.05	
1109.85/297.05	Arrrr..
1110.22/297.30	EOF