MAYBE
559.18/297.10	MAYBE
559.18/297.10	
559.18/297.10	We are left with following problem, upon which TcT provides the
559.18/297.10	certificate MAYBE.
559.18/297.10	
559.18/297.10	Strict Trs:
559.18/297.10	  { double(x) -> permute(x, x, a())
559.18/297.10	  , permute(x, y, a()) -> permute(isZero(x), x, b())
559.18/297.10	  , permute(y, x, c()) -> s(s(permute(x, y, a())))
559.18/297.10	  , permute(false(), x, b()) -> permute(ack(x, x), p(x), c())
559.18/297.10	  , permute(true(), x, b()) -> 0()
559.18/297.10	  , isZero(0()) -> true()
559.18/297.10	  , isZero(s(x)) -> false()
559.18/297.10	  , ack(0(), x) -> plus(x, s(0()))
559.18/297.10	  , ack(s(x), 0()) -> ack(x, s(0()))
559.18/297.10	  , ack(s(x), s(y)) -> ack(x, ack(s(x), y))
559.18/297.10	  , p(0()) -> 0()
559.18/297.10	  , p(s(x)) -> x
559.18/297.10	  , plus(x, 0()) -> x
559.18/297.10	  , plus(x, s(0())) -> s(x)
559.18/297.10	  , plus(x, s(s(y))) -> s(plus(s(x), y))
559.18/297.10	  , plus(0(), y) -> y
559.18/297.10	  , plus(s(x), y) -> plus(x, s(y)) }
559.18/297.10	Obligation:
559.18/297.10	  innermost runtime complexity
559.18/297.10	Answer:
559.18/297.10	  MAYBE
559.18/297.10	
559.18/297.10	None of the processors succeeded.
559.18/297.10	
559.18/297.10	Details of failed attempt(s):
559.18/297.10	-----------------------------
559.18/297.10	1) 'empty' failed due to the following reason:
559.18/297.10	   
559.18/297.10	   Empty strict component of the problem is NOT empty.
559.18/297.10	
559.18/297.10	2) 'Best' failed due to the following reason:
559.18/297.10	   
559.18/297.10	   None of the processors succeeded.
559.18/297.10	   
559.18/297.10	   Details of failed attempt(s):
559.18/297.10	   -----------------------------
559.18/297.10	   1) 'With Problem ... (timeout of 297 seconds)' failed due to the
559.18/297.10	      following reason:
559.18/297.10	      
559.18/297.10	      Computation stopped due to timeout after 297.0 seconds.
559.18/297.10	   
559.18/297.10	   2) 'Best' failed due to the following reason:
559.18/297.10	      
559.18/297.10	      None of the processors succeeded.
559.18/297.10	      
559.18/297.10	      Details of failed attempt(s):
559.18/297.10	      -----------------------------
559.18/297.10	      1) 'With Problem ... (timeout of 148 seconds) (timeout of 297
559.18/297.10	         seconds)' failed due to the following reason:
559.18/297.10	         
559.18/297.10	         None of the processors succeeded.
559.18/297.10	         
559.18/297.10	         Details of failed attempt(s):
559.18/297.10	         -----------------------------
559.18/297.10	         1) 'empty' failed due to the following reason:
559.18/297.10	            
559.18/297.10	            Empty strict component of the problem is NOT empty.
559.18/297.10	         
559.18/297.10	         2) 'With Problem ...' failed due to the following reason:
559.18/297.10	            
559.18/297.10	            None of the processors succeeded.
559.18/297.10	            
559.18/297.10	            Details of failed attempt(s):
559.18/297.10	            -----------------------------
559.18/297.10	            1) 'empty' failed due to the following reason:
559.18/297.10	               
559.18/297.10	               Empty strict component of the problem is NOT empty.
559.18/297.10	            
559.18/297.10	            2) 'Fastest' failed due to the following reason:
559.18/297.10	               
559.18/297.10	               None of the processors succeeded.
559.18/297.10	               
559.18/297.10	               Details of failed attempt(s):
559.18/297.10	               -----------------------------
559.18/297.10	               1) 'With Problem ...' failed due to the following reason:
559.18/297.10	                  
559.18/297.10	                  None of the processors succeeded.
559.18/297.10	                  
559.18/297.10	                  Details of failed attempt(s):
559.18/297.10	                  -----------------------------
559.18/297.10	                  1) 'empty' failed due to the following reason:
559.18/297.10	                     
559.18/297.10	                     Empty strict component of the problem is NOT empty.
559.18/297.10	                  
559.18/297.10	                  2) 'With Problem ...' failed due to the following reason:
559.18/297.10	                     
559.18/297.10	                     Empty strict component of the problem is NOT empty.
559.18/297.10	                  
559.18/297.10	               
559.18/297.10	               2) 'With Problem ...' failed due to the following reason:
559.18/297.10	                  
559.18/297.10	                  None of the processors succeeded.
559.18/297.10	                  
559.18/297.10	                  Details of failed attempt(s):
559.18/297.10	                  -----------------------------
559.18/297.10	                  1) 'empty' failed due to the following reason:
559.18/297.10	                     
559.18/297.10	                     Empty strict component of the problem is NOT empty.
559.18/297.10	                  
559.18/297.10	                  2) 'With Problem ...' failed due to the following reason:
559.18/297.10	                     
559.18/297.10	                     None of the processors succeeded.
559.18/297.10	                     
559.18/297.10	                     Details of failed attempt(s):
559.18/297.10	                     -----------------------------
559.18/297.10	                     1) 'empty' failed due to the following reason:
559.18/297.10	                        
559.18/297.10	                        Empty strict component of the problem is NOT empty.
559.18/297.10	                     
559.18/297.10	                     2) 'With Problem ...' failed due to the following reason:
559.18/297.10	                        
559.18/297.10	                        None of the processors succeeded.
559.18/297.10	                        
559.18/297.10	                        Details of failed attempt(s):
559.18/297.10	                        -----------------------------
559.18/297.10	                        1) 'empty' failed due to the following reason:
559.18/297.10	                           
559.18/297.10	                           Empty strict component of the problem is NOT empty.
559.18/297.10	                        
559.18/297.10	                        2) 'With Problem ...' failed due to the following reason:
559.18/297.10	                           
559.18/297.10	                           Empty strict component of the problem is NOT empty.
559.18/297.10	                        
559.18/297.10	                     
559.18/297.10	                  
559.18/297.10	               
559.18/297.10	            
559.18/297.10	         
559.18/297.10	      
559.18/297.10	      2) 'Best' failed due to the following reason:
559.18/297.10	         
559.18/297.10	         None of the processors succeeded.
559.18/297.10	         
559.18/297.10	         Details of failed attempt(s):
559.18/297.10	         -----------------------------
559.18/297.10	         1) 'bsearch-popstar (timeout of 297 seconds)' failed due to the
559.18/297.10	            following reason:
559.18/297.10	            
559.18/297.10	            The input cannot be shown compatible
559.18/297.10	         
559.18/297.10	         2) 'Polynomial Path Order (PS) (timeout of 297 seconds)' failed due
559.18/297.10	            to the following reason:
559.18/297.10	            
559.18/297.10	            The input cannot be shown compatible
559.18/297.10	         
559.18/297.10	      
559.18/297.10	      3) 'Fastest (timeout of 24 seconds) (timeout of 297 seconds)'
559.18/297.10	         failed due to the following reason:
559.18/297.10	         
559.18/297.10	         None of the processors succeeded.
559.18/297.10	         
559.18/297.10	         Details of failed attempt(s):
559.18/297.10	         -----------------------------
559.18/297.10	         1) 'Bounds with minimal-enrichment and initial automaton 'match''
559.18/297.10	            failed due to the following reason:
559.18/297.10	            
559.18/297.10	            match-boundness of the problem could not be verified.
559.18/297.10	         
559.18/297.10	         2) 'Bounds with perSymbol-enrichment and initial automaton 'match''
559.18/297.10	            failed due to the following reason:
559.18/297.10	            
559.18/297.10	            match-boundness of the problem could not be verified.
559.18/297.10	         
559.18/297.10	      
559.18/297.10	   
559.18/297.10	
559.18/297.10	
559.18/297.10	Arrrr..
559.18/297.14	EOF