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