MAYBE
201.16/60.02	MAYBE
201.16/60.02	
201.16/60.02	We are left with following problem, upon which TcT provides the
201.16/60.02	certificate MAYBE.
201.16/60.02	
201.16/60.02	Strict Trs:
201.16/60.02	  { a(x1) -> b(c(x1))
201.16/60.02	  , a(b(b(x1))) -> b(b(a(a(x1))))
201.16/60.02	  , b(a(x1)) -> x1 }
201.16/60.02	Obligation:
201.16/60.02	  derivational complexity
201.16/60.02	Answer:
201.16/60.02	  MAYBE
201.16/60.02	
201.16/60.02	None of the processors succeeded.
201.16/60.02	
201.16/60.02	Details of failed attempt(s):
201.16/60.02	-----------------------------
201.16/60.02	1) 'Fastest (timeout of 60 seconds)' failed due to the following
201.16/60.02	   reason:
201.16/60.02	   
201.16/60.02	   Computation stopped due to timeout after 60.0 seconds.
201.16/60.02	
201.16/60.02	2) 'Inspecting Problem... (timeout of 297 seconds)' failed due to
201.16/60.02	   the following reason:
201.16/60.02	   
201.16/60.02	   The weightgap principle applies (using the following nonconstant
201.16/60.02	   growth matrix-interpretation)
201.16/60.02	   
201.16/60.02	   TcT has computed the following triangular matrix interpretation.
201.16/60.02	   Note that the diagonal of the component-wise maxima of
201.16/60.02	   interpretation-entries contains no more than 1 non-zero entries.
201.16/60.02	   
201.16/60.02	     [a](x1) = [1] x1 + [0]
201.16/60.02	                           
201.16/60.02	     [b](x1) = [1] x1 + [2]
201.16/60.02	                           
201.16/60.02	     [c](x1) = [1] x1 + [1]
201.16/60.02	   
201.16/60.02	   The order satisfies the following ordering constraints:
201.16/60.02	   
201.16/60.02	           [a(x1)] =  [1] x1 + [0]    
201.16/60.02	                   ?  [1] x1 + [3]    
201.16/60.02	                   =  [b(c(x1))]      
201.16/60.02	                                      
201.16/60.02	     [a(b(b(x1)))] =  [1] x1 + [4]    
201.16/60.02	                   >= [1] x1 + [4]    
201.16/60.02	                   =  [b(b(a(a(x1))))]
201.16/60.02	                                      
201.16/60.02	        [b(a(x1))] =  [1] x1 + [2]    
201.16/60.02	                   >  [1] x1 + [0]    
201.16/60.02	                   =  [x1]            
201.16/60.02	                                      
201.16/60.02	   
201.16/60.02	   Further, it can be verified that all rules not oriented are covered by the weightgap condition.
201.16/60.02	   
201.16/60.02	   We are left with following problem, upon which TcT provides the
201.16/60.02	   certificate MAYBE.
201.16/60.02	   
201.16/60.02	   Strict Trs:
201.16/60.02	     { a(x1) -> b(c(x1))
201.16/60.02	     , a(b(b(x1))) -> b(b(a(a(x1)))) }
201.16/60.02	   Weak Trs: { b(a(x1)) -> x1 }
201.16/60.02	   Obligation:
201.16/60.02	     derivational complexity
201.16/60.02	   Answer:
201.16/60.02	     MAYBE
201.16/60.02	   
201.16/60.02	   The weightgap principle applies (using the following nonconstant
201.16/60.02	   growth matrix-interpretation)
201.16/60.02	   
201.16/60.02	   TcT has computed the following triangular matrix interpretation.
201.16/60.02	   Note that the diagonal of the component-wise maxima of
201.16/60.02	   interpretation-entries contains no more than 1 non-zero entries.
201.16/60.02	   
201.16/60.02	     [a](x1) = [1] x1 + [1]
201.16/60.02	                           
201.16/60.02	     [b](x1) = [1] x1 + [0]
201.16/60.02	                           
201.16/60.02	     [c](x1) = [1] x1 + [0]
201.16/60.02	   
201.16/60.02	   The order satisfies the following ordering constraints:
201.16/60.02	   
201.16/60.02	           [a(x1)] = [1] x1 + [1]    
201.16/60.02	                   > [1] x1 + [0]    
201.16/60.02	                   = [b(c(x1))]      
201.16/60.02	                                     
201.16/60.02	     [a(b(b(x1)))] = [1] x1 + [1]    
201.16/60.02	                   ? [1] x1 + [2]    
201.16/60.02	                   = [b(b(a(a(x1))))]
201.16/60.02	                                     
201.16/60.02	        [b(a(x1))] = [1] x1 + [1]    
201.16/60.02	                   > [1] x1 + [0]    
201.16/60.02	                   = [x1]            
201.16/60.02	                                     
201.16/60.02	   
201.16/60.02	   Further, it can be verified that all rules not oriented are covered by the weightgap condition.
201.16/60.02	   
201.16/60.02	   We are left with following problem, upon which TcT provides the
201.16/60.02	   certificate MAYBE.
201.16/60.02	   
201.16/60.02	   Strict Trs: { a(b(b(x1))) -> b(b(a(a(x1)))) }
201.16/60.02	   Weak Trs:
201.16/60.02	     { a(x1) -> b(c(x1))
201.16/60.02	     , b(a(x1)) -> x1 }
201.16/60.02	   Obligation:
201.16/60.02	     derivational complexity
201.16/60.02	   Answer:
201.16/60.02	     MAYBE
201.16/60.02	   
201.16/60.02	   None of the processors succeeded.
201.16/60.02	   
201.16/60.02	   Details of failed attempt(s):
201.16/60.02	   -----------------------------
201.16/60.02	   1) 'empty' failed due to the following reason:
201.16/60.02	      
201.16/60.02	      Empty strict component of the problem is NOT empty.
201.16/60.02	   
201.16/60.02	   2) 'Fastest' failed due to the following reason:
201.16/60.02	      
201.16/60.02	      None of the processors succeeded.
201.16/60.02	      
201.16/60.02	      Details of failed attempt(s):
201.16/60.02	      -----------------------------
201.16/60.02	      1) 'Fastest (timeout of 30 seconds)' failed due to the following
201.16/60.02	         reason:
201.16/60.02	         
201.16/60.02	         Computation stopped due to timeout after 30.0 seconds.
201.16/60.02	      
201.16/60.02	      2) 'Fastest' failed due to the following reason:
201.16/60.02	         
201.16/60.02	         None of the processors succeeded.
201.16/60.02	         
201.16/60.02	         Details of failed attempt(s):
201.16/60.02	         -----------------------------
201.16/60.02	         1) 'matrix interpretation of dimension 6' failed due to the
201.16/60.02	            following reason:
201.16/60.02	            
201.16/60.02	            The input cannot be shown compatible
201.16/60.02	         
201.16/60.02	         2) 'matrix interpretation of dimension 5' failed due to the
201.16/60.02	            following reason:
201.16/60.02	            
201.16/60.02	            The input cannot be shown compatible
201.16/60.02	         
201.16/60.02	         3) 'matrix interpretation of dimension 4' failed due to the
201.16/60.02	            following reason:
201.16/60.02	            
201.16/60.02	            The input cannot be shown compatible
201.16/60.02	         
201.16/60.02	         4) 'matrix interpretation of dimension 3' failed due to the
201.16/60.02	            following reason:
201.16/60.02	            
201.16/60.02	            The input cannot be shown compatible
201.16/60.02	         
201.16/60.02	         5) 'matrix interpretation of dimension 2' failed due to the
201.16/60.02	            following reason:
201.16/60.02	            
201.16/60.02	            The input cannot be shown compatible
201.16/60.02	         
201.16/60.02	         6) 'matrix interpretation of dimension 1' failed due to the
201.16/60.02	            following reason:
201.16/60.02	            
201.16/60.02	            The input cannot be shown compatible
201.16/60.02	         
201.16/60.02	      
201.16/60.02	      3) 'iteProgress' failed due to the following reason:
201.16/60.02	         
201.16/60.02	         Fail
201.16/60.02	      
201.16/60.02	      4) 'bsearch-matrix' failed due to the following reason:
201.16/60.02	         
201.16/60.02	         The input cannot be shown compatible
201.16/60.02	      
201.16/60.02	   
201.16/60.02	
201.16/60.02	3) 'iteProgress (timeout of 297 seconds)' failed due to the
201.16/60.02	   following reason:
201.16/60.02	   
201.16/60.02	   Fail
201.16/60.02	
201.16/60.02	4) 'bsearch-matrix (timeout of 297 seconds)' failed due to the
201.16/60.02	   following reason:
201.16/60.02	   
201.16/60.02	   The input cannot be shown compatible
201.16/60.02	
201.16/60.02	
201.16/60.02	Arrrr..
201.16/60.03	EOF